@blamejs/exceptd-skills 0.13.95 → 0.13.97

package/data/atlas-ttps.json

@@ -676,6 +676,8 @@
     "cve_refs": [
       "CVE-2023-51449",
       "CVE-2024-1561",
+      "CVE-2024-4889",
+      "CVE-2024-6587",
       "CVE-2026-42208",
       "MAL-2026-3083"
     ],
@@ -1616,7 +1618,9 @@
     "stix_id": "attack-pattern--801658f2-81cd-5935-93c7-5e6e2d80e669",
     "is_subtechnique": false,
     "cve_refs": [
-      "CVE-2023-48022"
+      "CVE-2023-48022",
+      "CVE-2025-64513",
+      "CVE-2026-26190"
     ]
   },
   "AML.T0036": {
@@ -1727,13 +1731,17 @@
       "CVE-2024-39722",
       "CVE-2024-42478",
       "CVE-2024-42479",
+      "CVE-2024-4889",
+      "CVE-2024-6587",
       "CVE-2025-30202",
       "CVE-2025-32444",
       "CVE-2025-64496",
+      "CVE-2025-64513",
       "CVE-2026-0766",
       "CVE-2026-24213",
       "CVE-2026-24214",
       "CVE-2026-24215",
+      "CVE-2026-26190",
       "CVE-2026-34159"
     ]
   },

package/data/attack-techniques.json

@@ -285,6 +285,7 @@
       "CVE-2024-21576",
       "CVE-2024-37032",
       "CVE-2024-42479",
+      "CVE-2024-4889",
       "CVE-2024-50050",
       "CVE-2025-1094",
       "CVE-2025-11837",
@@ -310,6 +311,7 @@
       "CVE-2026-24214",
       "CVE-2026-25592",
       "CVE-2026-26015",
+      "CVE-2026-26190",
       "CVE-2026-30615",
       "CVE-2026-30616",
       "CVE-2026-30617",
@@ -510,6 +512,7 @@
       "CVE-2025-34026",
       "CVE-2025-49706",
       "CVE-2025-61757",
+      "CVE-2025-64513",
       "CVE-2026-1603",
       "CVE-2026-20127",
       "CVE-2026-20182",
@@ -871,9 +874,11 @@
       "CVE-2024-42478",
       "CVE-2024-42479",
       "CVE-2024-43468",
+      "CVE-2024-4889",
       "CVE-2024-50050",
       "CVE-2024-56145",
       "CVE-2024-57726",
+      "CVE-2024-6587",
       "CVE-2024-7694",
       "CVE-2024-8069",
       "CVE-2025-10035",
@@ -971,6 +976,7 @@
       "CVE-2025-62848",
       "CVE-2025-64328",
       "CVE-2025-64496",
+      "CVE-2025-64513",
       "CVE-2025-6554",
       "CVE-2025-6558",
       "CVE-2025-66644",
@@ -1016,6 +1022,7 @@
       "CVE-2026-24215",
       "CVE-2026-25108",
       "CVE-2026-26015",
+      "CVE-2026-26190",
       "CVE-2026-30616",
       "CVE-2026-30617",
       "CVE-2026-30624",
@@ -1529,6 +1536,7 @@
     "name": "Unsecured Credentials: Credentials In Files",
     "version": "v19",
     "cve_refs": [
+      "CVE-2024-6587",
       "CVE-2025-21085",
       "CVE-2026-30615",
       "MAL-2026-3083",

package/data/cve-catalog.json

@@ -14542,6 +14542,425 @@
     "_intake_method": "manual-verified-curation",
     "_kev_short_description": "LlamaIndex's CLI builds a shell command from the --files argument and runs it unsanitized (CWE-78), executing arbitrary OS commands; fixed by adding shlex escaping."
   },
+  "CVE-2024-6587": {
+    "name": "BerriAI LiteLLM api_base SSRF API-Key Interception",
+    "type": "INFO-DISCLOSURE",
+    "cvss_score": 7.5,
+    "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
+    "cvss_note": "NVD/NIST CVSS v3.1 base 7.5 (HIGH, confidentiality-only); huntr.dev CNA scored the same. Server-side request forgery via the user-supplied api_base parameter (CWE-918).",
+    "cisa_kev": false,
+    "poc_available": true,
+    "poc_description": "Documented in the huntr.dev advisory and demonstrated at Pwn2Own as the SSRF link of a full-chain RCE: a request with a crafted api_base causes the proxy to forward the provider API key to the attacker.",
+    "ai_discovered": false,
+    "ai_discovery_source": "human_researcher",
+    "ai_discovery_notes": "Disclosed via huntr.dev. LiteLLM is a widely used LLM proxy/gateway that holds provider API keys for many models; the abused surface is its request/secret-management plane.",
+    "ai_assisted_weaponization": false,
+    "ai_assisted_notes": "No AI-assisted weaponization; SSRF in the LLM gateway.",
+    "active_exploitation": "none",
+    "active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation (CVE-2024-6587 was demonstrated at Pwn2Own as a research chain).",
+    "affected": "BerriAI LiteLLM before 1.44.8 (the api_base handling on POST /chat/completions); reported against 1.38.10, vulnerable range < 1.44.8 per GHSA-g26j-5385-hhw3, patched in 1.44.8.",
+    "affected_versions": [
+      "BerriAI LiteLLM < 1.44.8"
+    ],
+    "vector": "LiteLLM lets a user specify the api_base parameter on POST /chat/completions, and the proxy sends the request - including the configured provider API key - to that attacker-chosen domain (CWE-918 SSRF). A malicious user thereby intercepts the LLM provider API key the gateway holds. This SSRF was the first link in a Pwn2Own full-chain RCE against LiteLLM.",
+    "complexity": "low",
+    "complexity_notes": "NVD AV:N / AC:L. PR:N - unauthenticated request parameter.",
+    "patch_available": true,
+    "patch_required_reboot": false,
+    "live_patch_available": false,
+    "live_patch_tools": [],
+    "live_patch_notes": "Remediation is upgrading LiteLLM to 1.44.8 or later (validates api_base); redeploy, no host reboot.",
+    "vendor_update_paths": [
+      "Upgrade BerriAI LiteLLM to 1.44.8 or later. Restrict who can set request/config parameters, allow-list permitted api_base / provider endpoints, isolate the proxy's credential store, and do not expose the LiteLLM admin/config surface to untrusted users."
+    ],
+    "framework_control_gaps": {
+      "NIST-800-53-IA-2": "Authenticator (API key) management does not isolate the LLM gateway's stored provider keys from request-controlled egress; an SSRF exfiltrates them.",
+      "NIST-800-53-SI-2": "Flaw-remediation cadence does not track the LLM proxy/gateway as managed, credential-bearing software.",
+      "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the LLM gateway's request/secret-management plane as an SSRF / code-injection surface.",
+      "NIS2-Art21-patch-management": "Article 21 measures do not reach the LLM gateway as a privileged credential-holding control plane.",
+      "DORA-Art-9": "ICT protection measures do not model API-key exfiltration / code execution in an LLM gateway as an ICT-risk event.",
+      "UK-CAF-B2": "Identity and Access Control objective has no requirement to isolate the LLM gateway's provider credentials from request-controlled flows.",
+      "AU-ISM-1546": "Patch-application control does not single out LLM proxy/gateway software.",
+      "ALL-AI-PIPELINE-INTEGRITY": "No framework treats the LLM gateway as a high-value credential store whose request/config plane must be isolated; SSRF or config code-injection there yields mass key theft or proxy RCE."
+    },
+    "atlas_refs": [
+      "AML.T0049",
+      "AML.T0055"
+    ],
+    "attack_refs": [
+      "T1190",
+      "T1552.001"
+    ],
+    "rwep_score": 29,
+    "rwep_factors": {
+      "cisa_kev": 0,
+      "poc_available": 20,
+      "ai_factor": 0,
+      "active_exploitation": 0,
+      "blast_radius": 24,
+      "patch_available": -15,
+      "live_patch_available": 0,
+      "reboot_required": 0
+    },
+    "rwep_notes": "Standard (RWEP 29, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at/after disclosure (Hard Rule #3). poc_available=20 + blast_radius=24 (LiteLLM is a widely used LLM gateway holding provider keys) minus patch 15.",
+    "epss_score": null,
+    "epss_date": "2026-05-25",
+    "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
+    "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-6587",
+    "cwe_refs": [
+      "CWE-918"
+    ],
+    "iocs": {
+      "behavioral": [
+        "POST /chat/completions requests to LiteLLM carrying a user-supplied api_base pointing at a non-provider / attacker domain.",
+        "Outbound requests from the LiteLLM proxy (carrying provider API keys) to domains not on the approved provider allow-list.",
+        "Provider API keys appearing in traffic to unexpected endpoints.",
+        "BerriAI LiteLLM at BerriAI LiteLLM < 1.44.8 exposed to untrusted request/config input - the exposed precondition."
+      ],
+      "_ioc_source_note": "Behavioral signatures anchored to the huntr.dev advisory and the GitHub Security Advisory (https://github.com/advisories/GHSA-g26j-5385-hhw3), plus NVD CVE-2024-6587 (CWE-918). The user-supplied api_base egress carrying the provider key is the indicator anchor."
+    },
+    "source_verified": "2026-05-25",
+    "verification_sources": [
+      "https://nvd.nist.gov/vuln/detail/CVE-2024-6587",
+      "https://github.com/advisories/GHSA-g26j-5385-hhw3"
+    ],
+    "vendor_advisories": [
+      {
+        "vendor": "GitHub Security Advisory",
+        "advisory_id": "GHSA-g26j-5385-hhw3",
+        "url": "https://github.com/advisories/GHSA-g26j-5385-hhw3",
+        "severity": "high",
+        "published_date": "2024-09-13"
+      },
+      {
+        "vendor": "NVD",
+        "advisory_id": "CVE-2024-6587",
+        "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6587",
+        "severity": "high",
+        "published_date": "2024-09-13"
+      }
+    ],
+    "last_updated": "2026-05-25",
+    "discovery_attribution_note": "Manually curated from NVD (CWE-918; NIST CVSS 7.5) + the huntr.dev / GitHub advisory. BerriAI LiteLLM gateway flaw; same gateway credential-plane class as CVE-2026-42208 (shares NEW-CTRL-013).",
+    "_auto_imported": false,
+    "_intake_method": "manual-verified-curation",
+    "_kev_short_description": "BerriAI LiteLLM honors a user-supplied api_base on /chat/completions and forwards the configured provider API key to the attacker's domain (CWE-918 SSRF), leaking the gateway's keys."
+  },
+  "CVE-2024-4889": {
+    "name": "BerriAI LiteLLM Config Code Injection via UI_LOGO_PATH / KMS",
+    "type": "RCE",
+    "cvss_score": 7.2,
+    "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
+    "cvss_note": "NVD/NIST CVSS v3.1 base 7.2 (HIGH, PR:H); huntr.dev CNA scored the same. Code injection through unvalidated input in the secret-management dynamic-evaluation path (CWE-94).",
+    "cisa_kev": false,
+    "poc_available": true,
+    "poc_description": "Documented in the huntr.dev advisory: an admin-influenced UI_LOGO_PATH drives the secret-management code into evaluating attacker content.",
+    "ai_discovered": false,
+    "ai_discovery_source": "human_researcher",
+    "ai_discovery_notes": "Disclosed via huntr.dev. LiteLLM is a widely used LLM proxy/gateway that holds provider API keys for many models; the abused surface is its request/secret-management plane.",
+    "ai_assisted_weaponization": false,
+    "ai_assisted_notes": "No AI-assisted weaponization; code injection in the LLM gateway.",
+    "active_exploitation": "none",
+    "active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation (CVE-2024-6587 was demonstrated at Pwn2Own as a research chain).",
+    "affected": "BerriAI LiteLLM before 1.44.16.",
+    "affected_versions": [
+      "BerriAI LiteLLM < 1.44.16"
+    ],
+    "vector": "With Google KMS and SAVE_CONFIG_TO_DB configured, an admin-controlled UI_LOGO_PATH pointing at a remote server lets unvalidated input reach a dynamic-evaluation path in LiteLLM's secret-management code (CWE-94), allowing code execution on the proxy that holds the deployment's provider credentials.",
+    "complexity": "low",
+    "complexity_notes": "NVD AV:N / AC:L. PR:H - requires admin-level config influence.",
+    "patch_available": true,
+    "patch_required_reboot": false,
+    "live_patch_available": false,
+    "live_patch_tools": [],
+    "live_patch_notes": "Remediation is upgrading LiteLLM to 1.44.16 or later; redeploy, no host reboot.",
+    "vendor_update_paths": [
+      "Upgrade BerriAI LiteLLM to a patched release (1.44.16+). Restrict who can set request/config parameters, allow-list permitted api_base / provider endpoints, isolate the proxy's credential store, and do not expose the LiteLLM admin/config surface to untrusted users."
+    ],
+    "framework_control_gaps": {
+      "NIST-800-53-IA-2": "Authenticator (API key) management does not isolate the LLM gateway's stored provider keys from request-controlled egress; an SSRF exfiltrates them.",
+      "NIST-800-53-SI-2": "Flaw-remediation cadence does not track the LLM proxy/gateway as managed, credential-bearing software.",
+      "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the LLM gateway's request/secret-management plane as an SSRF / code-injection surface.",
+      "NIS2-Art21-patch-management": "Article 21 measures do not reach the LLM gateway as a privileged credential-holding control plane.",
+      "DORA-Art-9": "ICT protection measures do not model API-key exfiltration / code execution in an LLM gateway as an ICT-risk event.",
+      "UK-CAF-B2": "Identity and Access Control objective has no requirement to isolate the LLM gateway's provider credentials from request-controlled flows.",
+      "AU-ISM-1546": "Patch-application control does not single out LLM proxy/gateway software.",
+      "ALL-AI-PIPELINE-INTEGRITY": "No framework treats the LLM gateway as a high-value credential store whose request/config plane must be isolated; SSRF or config code-injection there yields mass key theft or proxy RCE."
+    },
+    "atlas_refs": [
+      "AML.T0049",
+      "AML.T0055"
+    ],
+    "attack_refs": [
+      "T1190",
+      "T1059"
+    ],
+    "rwep_score": 27,
+    "rwep_factors": {
+      "cisa_kev": 0,
+      "poc_available": 20,
+      "ai_factor": 0,
+      "active_exploitation": 0,
+      "blast_radius": 22,
+      "patch_available": -15,
+      "live_patch_available": 0,
+      "reboot_required": 0
+    },
+    "rwep_notes": "Standard (RWEP 27, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at/after disclosure (Hard Rule #3). poc_available=20 + blast_radius=22 (LiteLLM is a widely used LLM gateway holding provider keys) minus patch 15.",
+    "epss_score": null,
+    "epss_date": "2026-05-25",
+    "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
+    "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-4889",
+    "cwe_refs": [
+      "CWE-94"
+    ],
+    "iocs": {
+      "behavioral": [
+        "LiteLLM admin config changes setting UI_LOGO_PATH to a remote/attacker-controlled URL with KMS + SAVE_CONFIG_TO_DB enabled.",
+        "Code/process execution on the LiteLLM proxy host during config load or secret-management operations.",
+        "Outbound fetches from the LiteLLM proxy to unexpected hosts during configuration.",
+        "BerriAI LiteLLM at BerriAI LiteLLM < 1.44.16 exposed to untrusted request/config input - the exposed precondition."
+      ],
+      "_ioc_source_note": "Behavioral signatures anchored to the huntr.dev advisory and the GitHub Security Advisory (https://github.com/advisories/GHSA-423v-966v-frxg), plus NVD CVE-2024-4889 (CWE-94). The UI_LOGO_PATH/KMS dynamic-evaluation path is the indicator anchor."
+    },
+    "source_verified": "2026-05-25",
+    "verification_sources": [
+      "https://nvd.nist.gov/vuln/detail/CVE-2024-4889",
+      "https://github.com/advisories/GHSA-423v-966v-frxg"
+    ],
+    "vendor_advisories": [
+      {
+        "vendor": "GitHub Security Advisory",
+        "advisory_id": "GHSA-423v-966v-frxg",
+        "url": "https://github.com/advisories/GHSA-423v-966v-frxg",
+        "severity": "high",
+        "published_date": "2024-06-06"
+      },
+      {
+        "vendor": "NVD",
+        "advisory_id": "CVE-2024-4889",
+        "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-4889",
+        "severity": "high",
+        "published_date": "2024-06-06"
+      }
+    ],
+    "last_updated": "2026-05-25",
+    "discovery_attribution_note": "Manually curated from NVD (CWE-94; NIST CVSS 7.2) + the huntr.dev / GitHub advisory. BerriAI LiteLLM gateway flaw; same gateway credential-plane class as CVE-2026-42208 (shares NEW-CTRL-013).",
+    "_auto_imported": false,
+    "_intake_method": "manual-verified-curation",
+    "_kev_short_description": "BerriAI LiteLLM's secret-management path evaluates unvalidated input (UI_LOGO_PATH + KMS config, CWE-94), allowing an admin-influenced value to execute code on the credential-bearing proxy; fixed in 1.44.16."
+  },
+  "CVE-2025-64513": {
+    "name": "Milvus Proxy Authentication Bypass via Forged Headers",
+    "type": "AUTH-BYPASS",
+    "cvss_score": 9.3,
+    "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
+    "cvss_note": "CNA (GitHub) CVSS v4.0 base 9.3 (CRITICAL); NVD has not published its own assessed score. An unauthenticated attacker bypasses all authentication in the Milvus Proxy via forged HTTP headers (CWE-287).",
+    "cisa_kev": false,
+    "poc_available": true,
+    "poc_description": "Documented in the Milvus GitHub security advisory (GHSA-mhjq-8c7m-3f7p): an unauthenticated request with forged headers bypasses the Proxy's authentication.",
+    "ai_discovered": false,
+    "ai_discovery_source": "human_researcher",
+    "ai_discovery_notes": "Disclosed via the Milvus project's GitHub security advisories. Milvus is a widely used vector database that stores RAG embeddings and source data; the abused surface is its auth layer.",
+    "ai_assisted_weaponization": false,
+    "ai_assisted_notes": "No AI-assisted weaponization; authentication bypass on the vector database.",
+    "active_exploitation": "none",
+    "active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation. Note: exposed vector databases are widely reported to leak PII and credentials, so an auth bypass on RAG storage is high-impact.",
+    "affected": "Milvus before 2.4.24, 2.5.21, and 2.6.5 (the Proxy component).",
+    "affected_versions": [
+      "Milvus < 2.4.24",
+      "Milvus >= 2.5.0, < 2.5.21",
+      "Milvus >= 2.6.0, < 2.6.5"
+    ],
+    "vector": "Milvus's Proxy component trusts forged HTTP headers for authentication, so an unauthenticated attacker bypasses all authentication mechanisms (CWE-287) and gains full access to the vector database's collections and operations.",
+    "complexity": "low",
+    "complexity_notes": "AV:N / AC:L / PR:N - unauthenticated, network-reachable.",
+    "patch_available": true,
+    "patch_required_reboot": false,
+    "live_patch_available": false,
+    "live_patch_tools": [],
+    "live_patch_notes": "Remediation is upgrading Milvus to 2.4.24 / 2.5.21 / 2.6.5; redeploy, no host reboot.",
+    "vendor_update_paths": [
+      "Upgrade Milvus to a patched release (2.4.24 / 2.5.21 / 2.6.5). Enable authentication, replace any default tokens, and do not expose Milvus's Proxy / port 9091 to untrusted networks."
+    ],
+    "framework_control_gaps": {
+      "NIST-800-53-IA-2": "Identification-and-authentication is not enforced on the vector database's API/management surface; an unauthenticated attacker reaches RAG data.",
+      "NIST-800-53-SI-2": "Flaw-remediation cadence does not track the vector database (RAG persistence layer) as managed, auth-bypass-bearing software.",
+      "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the vector database's auth layer as an access-control surface.",
+      "NIS2-Art21-patch-management": "Article 21 measures do not reach the vector DB as a privileged data store.",
+      "DORA-Art-9": "ICT protection measures do not model an unauthenticated vector-DB takeover (RAG data / embeddings) as an ICT-risk event.",
+      "UK-CAF-B2": "Identity and Access Control objective has no requirement to authenticate the vector database storing RAG data.",
+      "AU-ISM-1546": "Patch-application control does not single out vector databases.",
+      "ALL-AI-PIPELINE-INTEGRITY": "No framework treats the vector database as a sensitive RAG data store whose API/management ports must authenticate; an auth bypass exposes embeddings, source documents, and enables RAG poisoning."
+    },
+    "atlas_refs": [
+      "AML.T0049",
+      "AML.T0035"
+    ],
+    "attack_refs": [
+      "T1190",
+      "T1078"
+    ],
+    "rwep_score": 27,
+    "rwep_factors": {
+      "cisa_kev": 0,
+      "poc_available": 20,
+      "ai_factor": 0,
+      "active_exploitation": 0,
+      "blast_radius": 22,
+      "patch_available": -15,
+      "live_patch_available": 0,
+      "reboot_required": 0
+    },
+    "rwep_notes": "Standard (RWEP 27, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3). poc_available=20 + blast_radius=22 (Milvus is a widely used vector database for RAG) minus patch 15. Note: unauthenticated access to RAG storage (PII/embeddings/source docs) raises operational urgency beyond the RWEP number.",
+    "epss_score": null,
+    "epss_date": "2026-05-25",
+    "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
+    "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2025-64513",
+    "cwe_refs": [
+      "CWE-287"
+    ],
+    "iocs": {
+      "behavioral": [
+        "Milvus Proxy requests carrying forged authentication headers from untrusted sources.",
+        "Vector-database collection reads/writes or admin operations not attributable to an authenticated client.",
+        "Milvus reachable from untrusted networks with default or weak tokens.",
+        "Milvus at any affected version (< 2.4.24, or 2.5.0-2.5.20, or 2.6.0-2.6.4) exposed to untrusted networks - the exposed precondition."
+      ],
+      "_ioc_source_note": "Behavioral signatures anchored to the Milvus GitHub security advisory (https://github.com/milvus-io/milvus/security/advisories/GHSA-mhjq-8c7m-3f7p) and NVD CVE-2025-64513 (CWE-287). The forged-header auth bypass is the indicator anchor."
+    },
+    "source_verified": "2026-05-25",
+    "verification_sources": [
+      "https://nvd.nist.gov/vuln/detail/CVE-2025-64513",
+      "https://github.com/milvus-io/milvus/security/advisories/GHSA-mhjq-8c7m-3f7p"
+    ],
+    "vendor_advisories": [
+      {
+        "vendor": "GitHub Security Advisory (milvus-io)",
+        "advisory_id": "GHSA-mhjq-8c7m-3f7p",
+        "url": "https://github.com/milvus-io/milvus/security/advisories/GHSA-mhjq-8c7m-3f7p",
+        "severity": "critical",
+        "published_date": "2025-11-10"
+      },
+      {
+        "vendor": "NVD",
+        "advisory_id": "CVE-2025-64513",
+        "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64513",
+        "severity": "critical",
+        "published_date": "2025-11-10"
+      }
+    ],
+    "last_updated": "2026-05-25",
+    "discovery_attribution_note": "Manually curated from NVD (CWE-287; CNA GitHub CVSS v4.0 9.3, no NVD-assessed score) + the Milvus GitHub advisory. Member of the Milvus vector-database authentication-bypass family (RAG persistence layer).",
+    "_auto_imported": false,
+    "_intake_method": "manual-verified-curation",
+    "_kev_short_description": "Milvus's Proxy trusts forged HTTP headers, letting an unauthenticated attacker bypass all authentication and access the vector database (CWE-287); fixed in 2.4.24 / 2.5.21 / 2.6.5."
+  },
+  "CVE-2026-26190": {
+    "name": "Milvus Port 9091 Missing Authentication / Weak Default Token",
+    "type": "RCE",
+    "cvss_score": 9.8,
+    "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
+    "cvss_note": "NVD CVSS v3.1 base 9.8 (CRITICAL). TCP port 9091 is exposed with weak default tokens and unauthenticated API access (CWE-306), enabling arbitrary expression evaluation and unauthenticated access to all business operations.",
+    "cisa_kev": false,
+    "poc_available": true,
+    "poc_description": "Documented in the Milvus GitHub security advisory (GHSA-7ppg-37fh-vcr6): an unauthenticated request to port 9091 reaches all business operations and arbitrary expression evaluation.",
+    "ai_discovered": false,
+    "ai_discovery_source": "human_researcher",
+    "ai_discovery_notes": "Disclosed via the Milvus project's GitHub security advisories. Milvus is a widely used vector database that stores RAG embeddings and source data; the abused surface is its auth layer.",
+    "ai_assisted_weaponization": false,
+    "ai_assisted_notes": "No AI-assisted weaponization; authentication bypass on the vector database.",
+    "active_exploitation": "none",
+    "active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation. Note: exposed vector databases are widely reported to leak PII and credentials, so an auth bypass on RAG storage is high-impact.",
+    "affected": "Milvus before 2.5.27, and 2.6.0 through 2.6.9.",
+    "affected_versions": [
+      "Milvus < 2.5.27",
+      "Milvus >= 2.6.0, <= 2.6.9"
+    ],
+    "vector": "Milvus exposes TCP port 9091 with weak default tokens and unauthenticated API access (CWE-306 missing authentication for a critical function). An unauthenticated attacker reaches all business operations and can trigger arbitrary expression evaluation, compromising the vector database and its RAG data.",
+    "complexity": "low",
+    "complexity_notes": "AV:N / AC:L / PR:N - unauthenticated, network-reachable.",
+    "patch_available": true,
+    "patch_required_reboot": false,
+    "live_patch_available": false,
+    "live_patch_tools": [],
+    "live_patch_notes": "Remediation is upgrading Milvus to 2.5.27 / 2.6.10; redeploy, no host reboot.",
+    "vendor_update_paths": [
+      "Upgrade Milvus to a patched release (2.5.27 / 2.6.10). Enable authentication, replace any default tokens, and do not expose Milvus's Proxy / port 9091 to untrusted networks."
+    ],
+    "framework_control_gaps": {
+      "NIST-800-53-IA-2": "Identification-and-authentication is not enforced on the vector database's API/management surface; an unauthenticated attacker reaches RAG data.",
+      "NIST-800-53-SI-2": "Flaw-remediation cadence does not track the vector database (RAG persistence layer) as managed, auth-bypass-bearing software.",
+      "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the vector database's auth layer as an access-control surface.",
+      "NIS2-Art21-patch-management": "Article 21 measures do not reach the vector DB as a privileged data store.",
+      "DORA-Art-9": "ICT protection measures do not model an unauthenticated vector-DB takeover (RAG data / embeddings) as an ICT-risk event.",
+      "UK-CAF-B2": "Identity and Access Control objective has no requirement to authenticate the vector database storing RAG data.",
+      "AU-ISM-1546": "Patch-application control does not single out vector databases.",
+      "ALL-AI-PIPELINE-INTEGRITY": "No framework treats the vector database as a sensitive RAG data store whose API/management ports must authenticate; an auth bypass exposes embeddings, source documents, and enables RAG poisoning."
+    },
+    "atlas_refs": [
+      "AML.T0049",
+      "AML.T0035"
+    ],
+    "attack_refs": [
+      "T1190",
+      "T1059"
+    ],
+    "rwep_score": 27,
+    "rwep_factors": {
+      "cisa_kev": 0,
+      "poc_available": 20,
+      "ai_factor": 0,
+      "active_exploitation": 0,
+      "blast_radius": 22,
+      "patch_available": -15,
+      "live_patch_available": 0,
+      "reboot_required": 0
+    },
+    "rwep_notes": "Standard (RWEP 27, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3). poc_available=20 + blast_radius=22 (Milvus is a widely used vector database for RAG) minus patch 15. Note: unauthenticated access to RAG storage (PII/embeddings/source docs) raises operational urgency beyond the RWEP number.",
+    "epss_score": null,
+    "epss_date": "2026-05-25",
+    "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
+    "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2026-26190",
+    "cwe_refs": [
+      "CWE-306"
+    ],
+    "iocs": {
+      "behavioral": [
+        "Unauthenticated requests to Milvus TCP port 9091 (metrics/management) reaching business operations or expression evaluation.",
+        "Vector-database collection reads/writes or admin operations not attributable to an authenticated client.",
+        "Milvus reachable from untrusted networks with default or weak tokens.",
+        "Milvus at any affected version (< 2.5.27, or 2.6.0-2.6.9) exposed to untrusted networks - the exposed precondition."
+      ],
+      "_ioc_source_note": "Behavioral signatures anchored to the Milvus GitHub security advisory (https://github.com/milvus-io/milvus/security/advisories/GHSA-7ppg-37fh-vcr6) and NVD CVE-2026-26190 (CWE-306). The unauthenticated port-9091 access is the indicator anchor."
+    },
+    "source_verified": "2026-05-25",
+    "verification_sources": [
+      "https://nvd.nist.gov/vuln/detail/CVE-2026-26190",
+      "https://github.com/milvus-io/milvus/security/advisories/GHSA-7ppg-37fh-vcr6"
+    ],
+    "vendor_advisories": [
+      {
+        "vendor": "GitHub Security Advisory (milvus-io)",
+        "advisory_id": "GHSA-7ppg-37fh-vcr6",
+        "url": "https://github.com/milvus-io/milvus/security/advisories/GHSA-7ppg-37fh-vcr6",
+        "severity": "critical",
+        "published_date": "2026-02-13"
+      },
+      {
+        "vendor": "NVD",
+        "advisory_id": "CVE-2026-26190",
+        "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26190",
+        "severity": "critical",
+        "published_date": "2026-02-13"
+      }
+    ],
+    "last_updated": "2026-05-25",
+    "discovery_attribution_note": "Manually curated from NVD (CWE-306; NIST CVSS 9.8) + the Milvus GitHub advisory. Member of the Milvus vector-database authentication-bypass family (RAG persistence layer).",
+    "_auto_imported": false,
+    "_intake_method": "manual-verified-curation",
+    "_kev_short_description": "Milvus exposes port 9091 with weak default tokens and unauthenticated API access (CWE-306), enabling arbitrary expression evaluation and full unauthenticated control; fixed in 2.5.27 / 2.6.10."
+  },
   "CVE-2026-41091": {
     "name": "Microsoft Defender (Malware Protection Engine) Link-Following LPE to SYSTEM",
     "type": "LPE",

package/data/cwe-catalog.json

@@ -379,6 +379,7 @@
       "CVE-2024-21513",
       "CVE-2024-21576",
       "CVE-2024-27132",
+      "CVE-2024-4889",
       "CVE-2024-56145",
       "CVE-2025-11837",
       "CVE-2025-1550",
@@ -702,6 +703,7 @@
       "CVE-2025-32975",
       "CVE-2025-3935",
       "CVE-2025-49706",
+      "CVE-2025-64513",
       "CVE-2026-20127",
       "CVE-2026-20182"
     ],
@@ -744,6 +746,7 @@
       "CVE-2025-61757",
       "CVE-2026-0300",
       "CVE-2026-24423",
+      "CVE-2026-26190",
       "CVE-2026-33017",
       "CVE-2026-39987",
       "CVE-2026-41940"
@@ -1849,6 +1852,7 @@
       "CVE-2023-43654",
       "CVE-2023-48022",
       "CVE-2023-51449",
+      "CVE-2024-6587",
       "CVE-2025-61884"
     ],
     "framework_controls_partially_addressing": [