CVE-2026-15378

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in the guardrails-detectors component. This vulnerability allows a remote attacker to perform a blind Server-Side Request Forgery (SSRF) by submitting a specially crafted XML Schema Definition (XSD) string. This can lead to unauthorized access to sensitive information, including credentials from cloud metadata services, Kubernetes API, internal MinIO, and other internal network endpoints. Additionally, it enables local file reads of critical data such as service account tokens and pod secrets.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 10, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Oct 3, 2026
Patch available. Sources: redhat.
Red Hat

2498941 – (CVE-2026-15378) CVE-2026-15378 guardrails-detectors: guardrails-detectors: SSRF and local file read via user-supplied XML Schema (xml-with-schema:)

https://bugzilla.redhat.com/show_bug.cgi?id=2498941
Red HatMentions a patch (unverified)

CVE-2026-15378 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-15378
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:73987
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:65126
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60520

Vendor Advisories for CVE-2026-15378(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-fms-guardrails-orchestrator-rhel9:17896566732026-09-30redhat
redhatrhoai/odh-fms-guardrails-orchestrator-rhel9:17867109632026-09-08redhat
redhatrhoai/odh-fms-guardrails-orchestrator-rhel9:17873602182026-08-27redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 63× 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 399 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 299 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15378?
CVE-2026-15378 is a critical-severity vulnerability; its CVE record was published on July 10, 2026. A flaw was found in the guardrails-detectors component. This vulnerability allows a remote attacker to perform a blind Server-Side Request Forgery (SSRF) by submitting a specially crafted XML Schema Definition (XSD) string. This can lead to unauthorized access to sensitive information, including…
When was CVE-2026-15378 made public?
CVE-2026-15378 was made public on July 10, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-15378 actively exploited?
CVE-2026-15378 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15378?
CVE-2026-15378 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15378?
A fix for CVE-2026-15378 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15378 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15378

Explore →

Is Your Infrastructure Affected by CVE-2026-15378?

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

Book a Demo →Browse All CVEs