CVE-2026-19233

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.6Exploit: None knownExposed: 0

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

CWE-918: Server-Side Request Forgery (SSRF) vulnerability exists that could cause unauthorized command execution and disclosure of server data when an attacker with a privileged account sends crafted, unvalidated parameters to a server endpoint.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity86% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

Vendor Advisories for CVE-2026-19233(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 24× in last 7d / 47× 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-09-20 20:53 UTCEG score recompute
  2. 2026-09-20 20:53 UTCGHSA enrichment
  3. 2026-09-20 09:00 UTCGHSA enrichment
  4. 2026-09-19 21:06 UTCEG score recompute
  5. 2026-09-19 21:06 UTCGHSA enrichment
  6. 2026-09-19 09:13 UTCGHSA enrichment
  7. 2026-09-18 21:19 UTCEG score recompute
  8. 2026-09-18 21:19 UTCGHSA enrichment
  9. 2026-09-18 19:27 UTCEPSS rescore
  10. 2026-09-18 08:53 UTCGHSA enrichment
  11. 2026-09-17 21:00 UTCEG score recompute
  12. 2026-09-17 21:00 UTCGHSA enrichment
  13. 2026-09-17 09:07 UTCGHSA enrichment
  14. 2026-09-16 21:13 UTCEG score recompute
  15. 2026-09-16 21:13 UTCGHSA enrichment
  16. 2026-09-16 14:07 UTCEPSS rescore
  17. 2026-09-16 08:54 UTCEG score recompute
  18. 2026-09-16 08:54 UTCGHSA enrichment
  19. 2026-09-16 05:14 UTCEPSS rescore
  20. 2026-09-15 20:15 UTCGHSA enrichment
  21. 2026-09-15 08:22 UTCEG score recompute
  22. 2026-09-15 08:22 UTCGHSA enrichment
  23. 2026-09-14 20:29 UTCGHSA enrichment
  24. 2026-09-14 08:36 UTCGHSA enrichment
  25. 2026-09-13 20:43 UTCEG score recompute
Show 22 more
  1. 2026-09-13 20:43 UTCGHSA enrichment
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-13 08:48 UTCGHSA enrichment
  4. 2026-09-12 20:55 UTCEG score recompute
  5. 2026-09-12 20:55 UTCGHSA enrichment
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-12 09:02 UTCGHSA enrichment
  8. 2026-09-11 21:08 UTCEG score recompute
  9. 2026-09-11 21:08 UTCGHSA enrichment
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-11 09:36 UTCEPSS rescore
  12. 2026-09-11 09:15 UTCGHSA enrichment
  13. 2026-09-10 21:22 UTCGHSA enrichment
  14. 2026-09-10 09:26 UTCGHSA enrichment
  15. 2026-09-09 21:30 UTCEG score recompute
  16. 2026-09-09 21:30 UTCGHSA enrichment
  17. 2026-09-09 20:55 UTCEG score recompute
  18. 2026-09-09 20:55 UTCGHSA enrichment
  19. 2026-09-09 20:33 UTCGHSA enrichment
  20. 2026-09-09 17:28 UTCEG score recompute
  21. 2026-09-09 16:37 UTCEG score recompute
  22. 2026-09-09 16:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19233?
CVE-2026-19233 is a high vulnerability published on September 9, 2026. CWE-918: Server-Side Request Forgery (SSRF) vulnerability exists that could cause unauthorized command execution and disclosure of server data when an attacker with a privileged account sends crafted, unvalidated parameters to a server endpoint.
When was CVE-2026-19233 disclosed?
CVE-2026-19233 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19233 actively exploited?
CVE-2026-19233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19233?
CVE-2026-19233 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-19233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19233, 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-19233

Explore →

Is Your Infrastructure Affected by CVE-2026-19233?

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