UTC

guardrails-ai

5 published advisories; version 0.5.10 or later fixes all but 2 of them.

Compromised releases

0.10.1 was published with malicious code. If it was installed, remove it, rotate every credential the environment could read, and pin dependencies by hash.

Hit by supply-chain campaigns: guardrails-ai 0.10.1 malicious release, Mini Shai-Hulud worm (2026).

Registry
PyPI
Advisories
5
Latest fix
0.5.10
Exploited in the wild
None listed
Advisories with no fix yet

2 advisories have no fixed release in any version yet. What can be done meanwhile:

From the advisory, shortened (GitHub Advisory Database, CC BY 4.0) · GHSA-xmpw-2vmm-p4p6
1. Pin to a safe version: guardrails-ai==0.10.0 2. While the PyPI quarantine is active, install from GitHub: pip install git+https://github.com/guardrails-ai/[email protected] The v0.10.0 tag in this repository is clean. Track quarantine status here: #1473. 3. If you installed 0.10.1, treat the host as potentially compromised. …

The full advisory →Licence

General guidance from ShieldPi, not a vendor fix

  • Compromised release. Move to a release the advisory names as clean, and rotate every credential, token and key the environment that ran the affected release could read.GHSA-xmpw-2vmm-p4p6
  • Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.GHSA-r6hf-g5x6-7pv9

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not guardrails-ai. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Provenance

Source: github.com/guardrails-ai/guardrails, named in the package metadata (not verified)

2 of the last 10 releases of guardrails-ai were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 0.11.0
  • 0.10.2
  • 0.10.0
  • 0.9.3
  • 0.9.2
  • 0.9.1
  • 0.8.2
  • 0.9.0
  • 0.8.1
  • 0.8.0

Green: published with provenance. Grey: without.

OpenSSF Scorecard has not scored this repository.

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
Malicious code in guardrails-ai (PyPI)GHSA-v3wf-vhp4-m47vCritical0.10.1Any other release2026-07-21
Malicious code in guardrails-ai 0.10.1 (supply chain compromise)CVE-2026-45758Critical= 0.10.1No fix yet2026-05-19
Guardrails AI contains a code injection vulnerability in its Hub package installation mechanismCVE-2026-31233Critical<= 0.6.7No fix yet2026-05-12
Guardrails has an arbitrary code execution vulnerabilityCVE-2024-45858High>= 0.2.9, < 0.5.100.5.102024-09-18
Guardrails AI vulnerable to Improper Restriction of XML External Entity ReferenceCVE-2024-6961High< 0.5.00.5.02024-07-21

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].