CVE-2026-45758

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-19. A secondary CVSS source baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-34912 (ENISA EUVD) · GHSA-xmpw-2vmm-p4p6 (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.6Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Malicious code in guardrails-ai 0.10.1 (supply chain compromise) · Advisory · guardrails-ai/guardrails · GitHub

https://github.com/guardrails-ai/guardrails/security/advisories/GHSA-xmpw-2vmm-p4p6
Web page

[SECURITY] Supply Chain Compromise in guardrails-ai v0.10.1 on PyPI · Issue #1473 · guardrails-ai/guardrails · GitHub

https://github.com/guardrails-ai/guardrails/issues/1473
Web page

guardrails/SECURITY_ADVISORY.md at main · guardrails-ai/guardrails · GitHub

https://github.com/guardrails-ai/guardrails/blob/main/SECURITY_ADVISORY.md

Vendor Advisories for CVE-2026-45758(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipguardrails-ai—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
guardrails-ai0.1.0 ... 0.9.3 (104 versions)
  • every version through 0.10.1: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 381 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 281 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 22:02 UTCEG score recompute
  2. 2026-11-02 22:02 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-11-01 20:25 UTCEG score recompute
  5. 2026-11-01 20:25 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  6. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-31 18:50 UTCEG score recompute
  8. 2026-10-31 18:50 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-30 17:13 UTCEG score recompute
  11. 2026-10-30 17:13 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  12. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-29 15:38 UTCEG score recompute
  15. 2026-10-29 15:38 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  16. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-28 13:45 UTCEG score recompute
  18. 2026-10-28 13:45 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  19. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-27 11:56 UTCEG score recompute
  21. 2026-10-27 11:56 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-26 10:20 UTCEG score recompute
  24. 2026-10-26 10:20 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  25. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 75 more
  1. 2026-10-25 14:26 UTCEG score recompute
  2. 2026-10-25 08:45 UTCEG score recompute
  3. 2026-10-25 08:45 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-24 07:08 UTCEG score recompute
  6. 2026-10-24 07:08 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  7. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-23 05:31 UTCEG score recompute
  9. 2026-10-23 05:31 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  10. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-22 03:53 UTCEG score recompute
  12. 2026-10-22 03:52 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-21 02:15 UTCEG score recompute
  15. 2026-10-21 02:14 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 00:37 UTCEG score recompute
  18. 2026-10-20 00:37 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-18 23:01 UTCEG score recompute
  21. 2026-10-18 23:01 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-18 03:37 UTCEG score recompute
  24. 2026-10-17 21:25 UTCEG score recompute
  25. 2026-10-17 21:24 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  26. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-16 19:46 UTCEG score recompute
  28. 2026-10-16 19:46 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  29. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-10-15 17:00 UTCEG score recompute
  31. 2026-10-15 17:00 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  32. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-10-14 11:02 UTCEG score recompute
  35. 2026-10-14 11:02 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  36. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-10-13 09:23 UTCEG score recompute
  38. 2026-10-13 09:23 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  39. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-10-12 16:04 UTCEG score recompute
  41. 2026-10-12 07:44 UTCGHSA enrichmentGHSA-xmpw-2vmm-p4p6 · GitHub severity CRITICAL · GitHub CVSS 9.6
  42. 2026-10-11 19:46 UTCEG score recompute
  43. 2026-10-11 17:00 UTCEG score recompute
  44. 2026-10-11 14:26 UTCEG score recompute
  45. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  51. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  52. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  57. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  61. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  64. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  66. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  67. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  68. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  69. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  70. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  71. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  72. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  73. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  74. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  75. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45758?
CVE-2026-45758 is a critical-severity vulnerability; its CVE record was published on May 19, 2026. 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…
When was the CVE record for CVE-2026-45758 published?
The CVE record for CVE-2026-45758 was published on May 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-45758 actively exploited?
CVE-2026-45758 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45758?
CVE-2026-45758 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45758?
The CVE record for CVE-2026-45758 names the fix: "Users should upgrade to version 0.10.2 or downgrade to version 0.10.0, both of which are unaffected." The vendor advisories EchelonGraph has for CVE-2026-45758 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45758

Explore →

Is Your Infrastructure Affected by CVE-2026-45758?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs