High

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

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.

Published Jul 6, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: WSO2

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

WSO2

Api Control Plane and 3 more

CVSS base

8.6

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Traffic Manager…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
WSO2	Api Control Plane	≥ 4.6.0 and < 4.6.0.19≥ 4.5.0 and < 4.5.0.55	Vulnerable	NIST National Vulnerability Database
WSO2	Api Control Plane	≥ 4.5.0 and < 4.5.0.55≥ 4.6.0 and < 4.6.0.19≥ 4.7.0 and < 4.7.0.2	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Api Manager	≥ 4.2.0 and < 4.2.0.194≥ 4.7.0 and < 4.7.0.2≥ 4.6.0 and < 4.6.0.18≥ 4.5.0 and < 4.5.0.54≥ 4.4.0 and < 4.4.0.69≥ 4.3.0 and < 4.3.0.105≥ 4.1.0 and < 4.1.0.254≥ 4.0.0 and < 4.0.0.390 and 2 more ≥ 3.2.0 and < 3.2.0.470≥ 3.2.1 and < 3.2.1.89	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Api Manager	≥ 4.6.0 and < 4.6.0.18≥ 4.5.0 and < 4.5.0.54≥ 4.4.0 and < 4.4.0.69≥ 4.3.0 and < 4.3.0.105≥ 4.2.0 and < 4.2.0.194≥ 4.1.0 and < 4.1.0.254≥ 4.0.0 and < 4.0.0.390	Vulnerable	NIST National Vulnerability Database
WSO2	Traffic Manager	≥ 4.5.0 and < 4.5.0.53≥ 4.6.0 and < 4.6.0.18	Vulnerable	NIST National Vulnerability Database
WSO2	Traffic Manager	≥ 4.7.0 and < 4.7.0.2≥ 4.6.0 and < 4.6.0.18≥ 4.5.0 and < 4.5.0.53	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Universal Gateway	≥ 4.5.0 and < 4.5.0.54≥ 4.6.0 and < 4.6.0.18	Vulnerable	NIST National Vulnerability Database
WSO2	Universal Gateway	≥ 4.5.0 and < 4.5.0.54≥ 4.6.0 and < 4.6.0.18≥ 4.7.0 and < 4.7.0.2	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.6	CVSS 3.1	High	3.9	4.0	ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
8.6	CVSS 3.1	High	—	—	WSO2 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-707

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · wso2/wso2 universal gateway, wso2/wso2 traffic manager, wso2/wso2 api control plane, wso2/wso2 api manager
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 8.6
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Jul 6, 2026 · WSO2

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

WSO2
every CVE for this vendor

CWE-707
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2025-5802 Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery Sep 15, 2026
Medium CVE-2026-4103 Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution Sep 14, 2026
Medium CVE-2026-3096 Reverse Tabnabbing via New Tab Navigation in Multiple WSO2 Products Allows Phishing and Credential Theft Sep 10, 2026
High CVE-2025-12737 Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution Sep 3, 2026
High CVE-2026-3416 Predictable Pseudorandom Number Generation via Webhook HMAC Secret Generation in Multiple WSO2 Products Allows Forged Event Payloads Sep 3, 2026
Critical CVE-2026-3418 Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution Aug 6, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-4249 is "Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption", rated High. It affects Api Control Plane (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.6 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.