WSO2 Universal Gateway: Improper Neutralization
CVE-2026-4249 is a high-severity improper neutralization vulnerability in WSO2 Universal Gateway from WSO2, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.5.0.54, 4.6.0.18, 4.7.0.2 as the first without the flaw, so updating WSO2 Universal Gateway to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WSO2 Universal Gateway to 4.5.0.54 or 4.6.0.18 or 4.7.0.2, whichever matches your release line, or a later version.
- Update WSO2 Traffic Manager to 4.5.0.53 or 4.6.0.18 or 4.7.0.2, whichever matches your release line, or a later version.
- Update WSO2 API Control Plane to 4.5.0.55 or 4.6.0.19 or 4.7.0.2, whichever matches your release line, or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 Universal Gateway | 4.5.0 up to, but not including, 4.5.0.54; 4.6.0 up to, but not including, 4.6.0.18; 4.7.0 up to, but not including, 4.7.0.2 | 4.5.0.54, 4.6.0.18, 4.7.0.2 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.53; 4.6.0 up to, but not including, 4.6.0.18; 4.7.0 up to, but not including, 4.7.0.2 | 4.5.0.53, 4.6.0.18, 4.7.0.2 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.55; 4.6.0 up to, but not including, 4.6.0.19; 4.7.0 up to, but not including, 4.7.0.2 | 4.5.0.55, 4.6.0.19, 4.7.0.2 |
| WSO2 | WSO2 API Manager | 3.2.0 up to, but not including, 3.2.0.470; 3.2.1 up to, but not including, 3.2.1.89; 4.0.0 up to, but not including, 4.0.0.390; 4.1.0 up to, but not including, 4.1.0.254; 4.2.0 up to, but not including, 4.2.0.194; 4.3.0 up to, but not including, 4.3.0.105; 4.4.0 up to, but not including, 4.4.0.69; 4.5.0 up to, but not including, 4.5.0.54; and 2 more ranges | 3.2.0.470, 3.2.1.89, 4.0.0.390, 4.1.0.254, 4.2.0.194, 4.3.0.105 |
| WSO2 | API Control Plane | 4.5.0 up to, but not including, 4.5.0.55; 4.6.0 up to, but not including, 4.6.0.19 | 4.5.0.55, 4.6.0.19 |
| WSO2 | API Manager | 4.0.0 up to, but not including, 4.0.0.390; 4.1.0 up to, but not including, 4.1.0.254; 4.2.0 up to, but not including, 4.2.0.194; 4.3.0 up to, but not including, 4.3.0.105; 4.4.0 up to, but not including, 4.4.0.69; 4.5.0 up to, but not including, 4.5.0.54; 4.6.0 up to, but not including, 4.6.0.18 | 4.0.0.390, 4.1.0.254, 4.2.0.194, 4.3.0.105, 4.4.0.69, 4.5.0.54 |
| WSO2 | Traffic Manager | 4.5.0 up to, but not including, 4.5.0.53; 4.6.0 up to, but not including, 4.6.0.18 | 4.5.0.53, 4.6.0.18 |
| WSO2 | Universal Gateway | 4.5.0 up to, but not including, 4.5.0.54; 4.6.0 up to, but not including, 4.6.0.18 | 4.5.0.54, 4.6.0.18 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H. Scored by CNA.
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization
The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being used when received from an upstream component, or before being sent to a downstream component.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in WSO2 Universal Gateway
- 8.7 High severity
- 9.4 Critical severity
- 8.4 High severity
- 9.1 Critical severity
- 8.7 High severity
- 9.0 Critical severity
Recent Improper Neutralization vulnerabilities
- 7.0 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.2 High severity
- 9.8 Critical severity
Spotted an error? Tell us.