CVE-2026-45758
A malicious version of the Guardrails AI Python framework (0.10.1) was published to PyPI on May 11, 2026. Users who installed that exact version from PyPI are at risk. The package was quickly quarantined and no data exfiltration was observed, but the risk remains.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Users who installed guardrails-ai version 0.10.1 from PyPI on May 11, 2026.
Real-world impact
An attacker could run arbitrary code on the victim’s machine, potentially exposing credentials such as GitHub PATs, cloud keys, or API tokens, and could create unauthorized GitHub workflows or repositories.
Why this severity
The CVSS score of 9.6 reflects a network‑accessible vulnerability that requires no special privileges, has a low attack complexity, and can compromise confidentiality, integrity, and availability if the malicious package is executed.
What to do about it
- 01Upgrade guardrails-ai to version 0.10.2 or downgrade to 0.10.0.
- 02Rotate any credentials that could be accessed from the machine (e.g., GitHub PATs, cloud provider keys, package registry tokens, API keys).
- 03Audit your GitHub account for unauthorized workflows or repositories.
NVD-referenced vendor advisory
Timeline
- Jun 5, 2026 · Jun 5, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 23, 2026 · 12d agoAdvisory updatedThe NVD record was last revised.
- Jul 24, 2026 · 11d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
How it’s attacked
References & advisories
- github.com/guardrails-ai/guardrails/bl…vendor advisory
- github.com/guardrails-ai/guardrails/is…issue tracking
- github.com/guardrails-ai/guardrails/se…mitigationvendor advisory