dbcve.org
Guardrails AiApplication · Guardrailsai

CVE-2026-45758

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Guardrails AI is a Python framework that helps build AI applications. On May 11, 2026 at approximately 6:00 PM Pacific, an attacker published a malicious version of `guardrails-ai` (0.10.1) to PyPI. Aany user who installed `guardrails-ai==0.10.1` from PyPI on May 11, 2026 may be affected. Security researchers identified the malicious package within approximately 2 hours of publication, and PyPI quarantined the repository. Based on our telemetry, Guardrails AI maintainers have observed no requests to Guardrails AI infrastructure originating from the malicious 0.10.1 version, and a review of system and access logs has produced no evidence of user data exfiltration through their systems. Users should upgrade to version 0.10.2 or downgrade to version 0.10.0, both of which are unaffected. Those who installed version 0.10.1 should rotate any credentials accessible from their machine (GitHub PATs, cloud provider keys, package registry tokens, API keys) and audit their GitHub account for unauthorized workflows or repositories.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a supply chain attack where a malicious version (0.10.1) of the guardrails-ai Python package was published to PyPI. Users who installed this version may have had arbitrary code executed on their systems, potentially leading to credential theft or unauthorized access.

MitigationImmediately upgrade to version 0.10.2 or downgrade to 0.10.0. Additionally, rotate all credentials present on affected machines (GitHub PATs, cloud keys, API tokens) and audit GitHub accounts for unauthorized activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Guardrails AiApplication
Affected:= 0.10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if guardrails-ai is installed
    Run `pip show guardrails-ai` or `pip list | grep guardrails`
    Affected if The package appears in the output at all (any version could potentially have been installed during the window)
  2. Identify the installed version
    Look at the Version field in the pip show output, or run `pip show guardrails-ai | grep Version`
    Affected if Version shows 0.10.1 specifically (the malicious version)
  3. Check installation date and source
    Run `pip show guardrails-ai` and check the 'Installed from' field, or review pip history logs if available with `pip list --format=freeze | grep guardrails`
    Affected if Package was installed from PyPI during or around May 11, 2026 and resolves to version 0.10.1
  4. Verify package integrity
    Run `pip hash -r $(python -c "import guardrails; print(guardrails.__file__)")` if the package imports, or manually inspect the installed package directory for unexpected files
    Affected if Any unexpected executable scripts, obfuscated files, or suspicious code in the package directory

A user is affected if guardrails-ai version 0.10.1 was installed from PyPI during the May 11, 2026 window (approximately 2 hours), as this version contained attacker-injected arbitrary code execution code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade to version 0.10.2 or downgrade to 0.10.0. Additionally, rotate all credentials present on affected machines (GitHub PATs, cloud keys, API tokens) and audit GitHub accounts for unauthorized activity.

Recommended fix High confidence

guardrails-ai 0.10.2

  1. Check if guardrails-ai version 0.10.1 is currently installed using: pip show guardrails-ai
  2. If version 0.10.1 is installed, immediately uninstall it: pip uninstall guardrails-ai
  3. Install the safe version 0.10.2: pip install guardrails-ai==0.10.2
  4. Verify the installed version is no longer 0.10.1: pip show guardrails-ai
  5. If version 0.10.1 was installed, rotate all credentials that were accessible from the affected machine including GitHub personal access tokens, cloud provider API keys, package registry tokens, and any other API keys
  6. Audit your GitHub account for any unauthorized workflows, repositories, or suspicious activity

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Guardrails Ai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45758 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data