CVE-2026-4249
published 2026-07-06CVE-2026-4249: The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and…
PriorityP354high8.6CVSS 3.1
AVNACLPRNUINSCCNINAH
EPSS
0.56%
45.2th percentile
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.
Affected
32 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| wso2 | api_control_plane | >= 4.5.0 < 4.5.0.55 | 4.5.0.55 |
| wso2 | api_control_plane | >= 4.6.0 < 4.6.0.19 | 4.6.0.19 |
| wso2 | api_manager | >= 4.0.0 < 4.0.0.390 | 4.0.0.390 |
| wso2 | api_manager | >= 4.1.0 < 4.1.0.254 | 4.1.0.254 |
| wso2 | api_manager | >= 4.2.0 < 4.2.0.194 | 4.2.0.194 |
| wso2 | api_manager | >= 4.3.0 < 4.3.0.105 | 4.3.0.105 |
| wso2 | api_manager | >= 4.4.0 < 4.4.0.69 | 4.4.0.69 |
| wso2 | api_manager | >= 4.5.0 < 4.5.0.54 | 4.5.0.54 |
| wso2 | api_manager | >= 4.6.0 < 4.6.0.18 | 4.6.0.18 |
| wso2 | traffic_manager | >= 4.5.0 < 4.5.0.53 | 4.5.0.53 |
| wso2 | traffic_manager | >= 4.6.0 < 4.6.0.18 | 4.6.0.18 |
| wso2 | universal_gateway | >= 4.5.0 < 4.5.0.54 | 4.5.0.54 |
| wso2 | universal_gateway | >= 4.6.0 < 4.6.0.18 | 4.6.0.18 |
| wso2 | wso2_api_control_plane | >= 4.5.0 < 4.5.0.55 | 4.5.0.55 |
| wso2 | wso2_api_control_plane | >= 4.6.0 < 4.6.0.19 | 4.6.0.19 |
| wso2 | wso2_api_control_plane | >= 4.7.0 < 4.7.0.2 | 4.7.0.2 |
| wso2 | wso2_api_manager | >= 3.2.0 < 3.2.0.470 | 3.2.0.470 |
| wso2 | wso2_api_manager | >= 3.2.1 < 3.2.1.89 | 3.2.1.89 |
| wso2 | wso2_api_manager | >= 4.0.0 < 4.0.0.390 | 4.0.0.390 |
| wso2 | wso2_api_manager | >= 4.1.0 < 4.1.0.254 | 4.1.0.254 |
| wso2 | wso2_api_manager | >= 4.2.0 < 4.2.0.194 | 4.2.0.194 |
| wso2 | wso2_api_manager | >= 4.3.0 < 4.3.0.105 | 4.3.0.105 |
| wso2 | wso2_api_manager | >= 4.4.0 < 4.4.0.69 | 4.4.0.69 |
| wso2 | wso2_api_manager | >= 4.5.0 < 4.5.0.54 | 4.5.0.54 |
| wso2 | wso2_api_manager | >= 4.6.0 < 4.6.0.18 | 4.6.0.18 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
WSO2 API Gateway Throttling Event Handling denial of service (EUVD-2026-41871 / WID-SEC-2026-2085)
vuldb·2026-08-06·CVSS 8.6
CVE-2026-4249 [HIGH] WSO2 API Gateway Throttling Event Handling denial of service (EUVD-2026-41871 / WID-SEC-2026-2085)
A vulnerability labeled as problematic has been found in WSO2 API Gateway. This vulnerability affects unknown code of the component Throttling Event Handling. Executing a manipulation can lead to denial of service.
This vulnerability is handled as CVE-2026-4249. The attack can be executed remotely. There is not any exploit available.
GHSA
The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content.
ghsa_unreviewed·2026-07-06
CVE-2026-4249 [HIGH] CWE-707 The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content.
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-07-06
Published