CVE-2026-45758: Guardrails AI supply chain compromise via PyPI release
guardrails-ai
An attacker published a malicious version of the guardrails-ai package to PyPI, which was quarantined shortly after. Telemetry shows no evidence of data exfiltration or active exploitation.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.6
- EPSS
- <0.01 · top 80% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 19 May 2026
- last update
- 19 May 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-05-19CVE-2026-45758: Malicious code in guardrails-ai 0.10.1 (supply chain compromise)GitHub Advisory Database · github.com/advisories/GHSA-xmpw-2vmm-p4p6
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Supply chain
- AI role
- Attack on AI
- categories
- Supply chain
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- AML.T0010 AI Supply Chain Compromise
- dates
- happened 11 May 2026 · first reported 19 May 2026
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-45758: Guardrails AI supply chain compromise via PyPI release https://gcdradar.vercel.app/incidents/cve-2026-45758-guardrails-ai-supply-chain-compromise-via-pyp · AIR-2026-0709 · closed 2026-05-19 - Lane: Supply chain - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-05-19 (happened 2026-05-11) - AI role: Attack on AI - Products: guardrails-ai - CVE ids: CVE-2026-45758 - CVSS: 9.6 ## Summary An attacker published a malicious version of the guardrails-ai package to PyPI, which was quarantined shortly after. Telemetry shows no evidence of data exfiltration or active exploitation. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-05-19: CVE-2026-45758: Malicious code in guardrails-ai 0.10.1 (supply chain compromise) (https://github.com/advisories/GHSA-xmpw-2vmm-p4p6) ## Sources - 2026-05-19 GitHub Advisory Database: CVE-2026-45758: Malicious code in guardrails-ai 0.10.1 (supply chain compromise) https://github.com/advisories/GHSA-xmpw-2vmm-p4p6 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.5vLLM CVE-2026-41523: vLLM Security Check Bypass via assert Statement
Patch now · Disclosed · since 16 Jun 2026 · updated 22 Jun 2026 · CVE-2026-41523
AI - closed6.5vLLM CVE-2026-47155: vLLM artifact pin decay allows loading unpinned code and weights
Patch now · Disclosed · since 10 Jun 2026 · updated 22 Jun 2026 · CVE-2026-47155
AI - closed8.8vLLM vLLM Hardcoded Trust Remote Code Parameter Leads to RCE
Patch now · Disclosed · since 28 May 2026 · CVE-2026-4944
AI - closed8.8vLLM CVE-2026-5817: Docker Model Runner vllm-metal arbitrary code execution vulnerability
Patch now · Disclosed · since 22 May 2026 · CVE-2026-5817
AI - closed9.8Guardrails AI CVE-2026-31233: Guardrails AI code injection in Hub installer
Supply chain · Disclosed · since 12 May 2026 · CVE-2026-31233
AI - closed8.2LangChain family CVE-2026-44843: LangChain vulnerable to unsafe deserialization
Patch now · Disclosed · since 8 May 2026 · updated 26 May 2026 · CVE-2026-44843
AI