CVE-2026-4249
Unauthenticated JSON can trigger persistent DoS in WSO2 throttling.
Is CVE-2026-4249 being exploited?
Not confirmed. CVE-2026-4249 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.
How severe is CVE-2026-4249?
CVE-2026-4249 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4249?
Yes. A fix has been recorded for CVE-2026-4249. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4249 affect?
CVE-2026-4249 affects WSO2 API Manager, WSO2 API Gateway, WSO2 Product Suite. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4249?
Apply vendor patch to fix JSON validation in throttling
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can inject JSON data to cause a persistent DoS, blocking API traffic and reducing availability.
Immediate action required
- affected>= 4.5.0 and < 4.5.0.55
- affected>= 4.6.0 and < 4.6.0.19
- affected>= 4.7.0 and < 4.7.0.2
- affected< 3.2.0
- affected>= 3.2.0 and < 3.2.0.470
- affected>= 3.2.1 and < 3.2.1.89
- affected>= 4.0.0 and < 4.0.0.390
- affected>= 4.1.0 and < 4.1.0.254
- affected>= 4.2.0 and < 4.2.0.194
- affected>= 4.3.0 and < 4.3.0.105
- affected>= 4.4.0 and < 4.4.0.69
- affected>= 4.5.0 and < 4.5.0.54
- affected>= 4.6.0 and < 4.6.0.18
- affected>= 4.7.0 and < 4.7.0.2
- affected>= 4.5.0 and < 4.5.0.53
- affected>= 4.6.0 and < 4.6.0.18
- affected>= 4.7.0 and < 4.7.0.2
- affected>= 4.5.0 and < 4.5.0.54
- affected>= 4.6.0 and < 4.6.0.18
- affected>= 4.7.0 and < 4.7.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.