Guardrails AI
Filed as: guardrails-ai
Records
4
Disclosed CVEs
4
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2026-05-19 · 4 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for Guardrails AI has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
█
Nov ’242 disclosed · peak 2 in May ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 4
- 2026-05-19CVE-2026-45758CVE-2026-45758: Guardrails AI supply chain compromise via PyPI release2 Disclosedguardrails-ai · pypi
- 2026-05-12CVE-2026-31233CVE-2026-31233: Guardrails AI code injection in Hub installer2 Disclosedcode-injection · rce
- 2024-09-18CVE-2024-45858CVE-2024-45858: Guardrails arbitrary code execution vulnerability2 Disclosedcode-execution · guardrails-ai
- 2024-07-21
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.