CVE-2026-4249

HIGHPre-NVD 8.68.6
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. a secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: NoneExposed: 0

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

The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a persistent denial of service condition.

Successful exploitation of this vulnerability can disrupt the API Gateway, preventing legitimate API traffic from being processed and impacting complete service availability. The denial of service is persistent, requiring manual intervention to restore normal operations.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
43(Track)
EG Risk 43/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
26.3%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 6, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-4249(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 10× in last 7d / 44× 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-23 03:11 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 21:17 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 09:53 UTCGHSA enrichment
  12. 2026-07-15 22:29 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 11:06 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 23:41 UTCGHSA enrichment
  19. 2026-07-14 12:17 UTCGHSA enrichment
  20. 2026-07-14 00:53 UTCGHSA enrichment
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 13:29 UTCGHSA enrichment
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 02:04 UTCGHSA enrichment
  25. 2026-07-12 14:39 UTCGHSA enrichment
Show 19 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 03:15 UTCGHSA enrichment
  3. 2026-07-11 15:50 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 04:26 UTCGHSA enrichment
  6. 2026-07-10 17:02 UTCGHSA enrichment
  7. 2026-07-10 05:37 UTCGHSA enrichment
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 18:11 UTCGHSA enrichment
  10. 2026-07-09 06:45 UTCGHSA enrichment
  11. 2026-07-08 19:21 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 07:57 UTCGHSA enrichment
  14. 2026-07-07 20:33 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 09:10 UTCGHSA enrichment
  17. 2026-07-06 21:46 UTCGHSA enrichment
  18. 2026-07-06 10:22 UTCEG score recompute
  19. 2026-07-06 10:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-4249?
CVE-2026-4249 is a high vulnerability published on July 6, 2026. The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a persistent denial of service condition.…
When was CVE-2026-4249 disclosed?
CVE-2026-4249 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 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-4249 actively exploited?
CVE-2026-4249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4249?
CVE-2026-4249 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-4249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4249, 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-4249

Explore →

Is Your Infrastructure Affected by CVE-2026-4249?

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