Malicious PyPI package in Guardrails AI 0.10.1
CVE-2026-45758 concerns a malicious publication of the Python package guardrails-ai version 0.10.1 to PyPI. On 2026-05-11 at approximately 18:00 Pacific, an attacker published the malicious 0.10.1 release. Any user who installed guardrails-ai==0.10.1 from PyPI on that date may have been exposed. The package was identified as malicious by security researchers within about two hours, after which PyPI quarantined the repository. The available information indicates this is a software supply-chain compromise affecting a specific package version rather than a flaw in the legitimate Guardrails AI codebase. The malicious package could access credentials available on the installing machine and may have targeted developer environments and associated GitHub resources.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
guardrails-ai==0.10.1 from PyPI. If installation status is uncertain, verify package versions across developer endpoints, build systems, and CI/CD pipelines. Restrict and minimize credentials present on developer machines and runners, use short-lived tokens where possible, and monitor GitHub and cloud accounts for anomalous activity. Organizations should validate package provenance, pin to trusted versions, and use repository and dependency monitoring controls to detect malicious or unexpected package releases.Remediation
Patch, then assume compromise.
guardrails-ai version 0.10.2 or downgrade to version 0.10.0, both of which are identified as unaffected. Any system on which guardrails-ai==0.10.1 was installed should be treated as potentially exposed: rotate all credentials that may have been accessible from that machine, including GitHub PATs, cloud provider credentials, package registry tokens, and API keys. Review GitHub accounts and organizations for unauthorized workflows, repositories, or other suspicious changes, and perform broader incident-response validation on affected developer workstations or CI environments as appropriate.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.