CVE-2026-15378

CRITICALPre-NVD 9.39.3
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(high)
EPSS
34.3%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 10, 2026
Patch available. Sources: redhat.
redhat

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
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-15378

Vendor Advisories for CVE-2026-15378(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-13 14:18 UTCEG score recompute
  2. 2026-07-13 14:18 UTCGHSA enrichment
  3. 2026-07-13 10:06 UTCEG score recompute
  4. 2026-07-13 10:06 UTCGHSA enrichment
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-13 05:44 UTCEG score recompute
  7. 2026-07-13 05:44 UTCGHSA enrichment
  8. 2026-07-13 01:30 UTCEG score recompute
  9. 2026-07-13 01:30 UTCGHSA enrichment
  10. 2026-07-12 21:17 UTCEG score recompute
  11. 2026-07-12 21:17 UTCGHSA enrichment
  12. 2026-07-12 17:04 UTCEG score recompute
  13. 2026-07-12 17:04 UTCGHSA enrichment
  14. 2026-07-12 12:51 UTCEG score recompute
  15. 2026-07-12 12:51 UTCGHSA enrichment
  16. 2026-07-12 08:38 UTCEG score recompute
  17. 2026-07-12 08:38 UTCGHSA enrichment
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-12 04:25 UTCEG score recompute
  20. 2026-07-12 04:25 UTCGHSA enrichment
  21. 2026-07-12 00:11 UTCEG score recompute
  22. 2026-07-12 00:11 UTCGHSA enrichment
  23. 2026-07-11 19:56 UTCEG score recompute
  24. 2026-07-11 19:56 UTCGHSA enrichment
  25. 2026-07-11 15:43 UTCEG score recompute
Show 16 more
  1. 2026-07-11 15:42 UTCGHSA enrichment
  2. 2026-07-11 11:29 UTCEG score recompute
  3. 2026-07-11 11:29 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 07:16 UTCEG score recompute
  6. 2026-07-11 07:16 UTCGHSA enrichment
  7. 2026-07-11 03:03 UTCEG score recompute
  8. 2026-07-11 03:03 UTCGHSA enrichment
  9. 2026-07-10 22:49 UTCEG score recompute
  10. 2026-07-10 22:49 UTCGHSA enrichment
  11. 2026-07-10 18:36 UTCEG score recompute
  12. 2026-07-10 18:36 UTCGHSA enrichment
  13. 2026-07-10 14:23 UTCEG score recompute
  14. 2026-07-10 14:23 UTCGHSA enrichment
  15. 2026-07-10 10:08 UTCEG score recompute
  16. 2026-07-10 10:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15378?
CVE-2026-15378 is a critical vulnerability 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 disclosed?
CVE-2026-15378 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15378 actively exploited?
CVE-2026-15378 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15378?
CVE-2026-15378 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-15378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15378, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.