# CVE-2026-31233: Guardrails AI contains a code injection vulnerability in its Hub package installation mechanism

> Attackers can execute arbitrary code by publishing malicious packages to the Guardrails Hub, affecting users who install them.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-r6hf-g5x6-7pv9, PYSEC-2026-347

## What is CVE-2026-31233?

CVE-2026-31233 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-31233?

3 open source packages ship an affected version, including guardrails-ai.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `guardrails-ai` | PyPI | All versions to 0.6.7 | None |
| `guardrails-ai` | PyPI | All versions to 0.6.7 | None |
| `guardrails-ai` | PyPI | All versions to 0.6.7 | None |

## How do I fix CVE-2026-31233?

No fix has been published for CVE-2026-31233 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31233 being exploited?

There is no known exploitation of CVE-2026-31233 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31233 and fix it if it is affected.

What it is: CVE-2026-31233 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31233 in the wild and no public exploit code.

Affected packages and fixed versions:
- guardrails-ai (PyPI): affected all versions up to 0.6.7; no fix listed
- guardrails-ai (PyPI): affected all versions up to 0.6.7; no fix listed
- guardrails-ai (PyPI): affected all versions up to 0.6.7; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31233/ (Markdown: https://insights.sbomify.com/CVE-2026-31233/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31233
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31233
- OSV: https://osv.dev/vulnerability/CVE-2026-31233

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31233/
Summaries are generated and may contain mistakes; the official description above is the record.