Skip to content
Fencer Intel
high 8.6

CVE-2026-4249 json

Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption

published 4mo ago modified 4mo ago also EUVD-2026-41871

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • WSO2 WSO2 Universal Gateway 4.5.0.54, 4.6.0.18, 4.7.0.2
  • WSO2 WSO2 Traffic Manager 4.5.0.53, 4.6.0.18, 4.7.0.2
  • WSO2 WSO2 API Control Plane 4.5.0.55, 4.6.0.19, 4.7.0.2
  • WSO2 WSO2 API Manager 3.2.0.470, 3.2.1.89, 4.0.0.390, 4.1.0.254, 4.2.0.194, 4.3.0.105, 4.4.0.69, 4.5.0.54, 4.6.0.18, 4.7.0.2

Is CVE-2026-4249 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Affected products

  • WSO2 WSO2 Universal Gateway
  • WSO2 WSO2 Traffic Manager
  • WSO2 WSO2 API Control Plane
  • WSO2 WSO2 API Manager

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.