dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-31233

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-12
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 Zero-click

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 thru 0.6.7 contains a code injection vulnerability (CWE-94) in its Hub package installation mechanism. When installing validator packages via guardrails hub install, the system retrieves a manifest from the Guardrails Hub and dynamically executes a script specified in the post_install field. The script path is constructed from untrusted manifest data and executed without proper validation or sanitization, allowing remote code execution. An attacker who can publish malicious packages to the Hub can inject arbitrary code that will be executed on any system where a victim installs the malicious package.

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

Guardrails AI through 0.6.7 has a code injection vulnerability in its Hub package installation mechanism. The system retrieves a manifest from the Guardrails Hub containing a post_install field, constructs a script path from untrusted manifest data, and executes it without validation or sanitization. An attacker who publishes a malicious package to the Hub can achieve remote code execution on any victim who installs that package.

MitigationImmediately upgrade to version 0.6.8 or later which implements proper validation and sanitization of manifest script paths. Until patched, avoid installing untrusted packages from the Guardrails Hub and verify the provenance of all packages before installation.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Determine installed Guardrails AI version
    Run 'pip show guardrails-ai' or 'pip list | grep guardrails' to retrieve the installed version number
    Affected if Version is 0.6.7 or lower (any version through 0.6.7 is affected)
  2. Identify Guardrails Hub package installations
    Look for any Guardrails Hub packages installed in your environment. Check your requirements.txt, environment lock files, or run 'pip list' and review any packages sourced from the Guardrails Hub
    Affected if Any packages from the Guardrails Hub have been installed in the environment
  3. Inspect package manifests for post_install scripts
    If Hub packages are installed, examine their manifests or metadata files for the presence of a 'post_install' field. On Linux, check installed package directories under site-packages for any manifest or metadata files
    Affected if Any installed package manifest contains a post_install field pointing to a script path
  4. Review recent package installation logs
    Check command history, installation logs, or Guardrails activity logs for any package installation events from the Guardrails Hub. Look for any executed post-installation scripts
    Affected if Package installation logs show execution of post-install scripts during Hub package setup

You are likely affected if Guardrails AI version is 0.6.7 or earlier AND any packages have been installed from the Guardrails Hub, because the vulnerability triggers during Hub package installation without requiring additional configuration.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade to version 0.6.8 or later which implements proper validation and sanitization of manifest script paths. Until patched, avoid installing untrusted packages from the Guardrails Hub and verify the provenance of all packages before installation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31233 — 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-31233 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