Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-4249: The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without

47
This month
HIGH 8.6REMOTEUPGRADEUPGRADEUPGRADE

CVE-2026-4249 is a high-severity flaw (CVSS 8.6) affecting api control plane, api manager, traffic manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 compl

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 54%)
CISA exploited listNo
WeaknessCWE-707
Published2026-07-06
Last modified2026-07-09
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

Last updated 2026-07-09 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

wso2 api control plane UPGRADE
Affected: >= 4.5.0 and < 4.5.0.55 · >= 4.6.0 and < 4.6.0.19
Fixed in: 4.5.0.55, 4.6.0.19
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy api-control-plane || rpm -q api-control-plane || api-control-plane --version
2. UPGRADE to 4.5.0.55 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade api-control-plane
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade api-control-plane
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison api-control-plane sudo apt install api-control-plane=<VERSION_BEFORE_4.5.0> sudo apt-mark hold api-control-plane
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-control-plane sudo dnf downgrade api-control-plane-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add api-control-plane
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 api manager UPGRADE
Affected: >= 4.0.0 and < 4.0.0.390 · >= 4.1.0 and < 4.1.0.254 · >= 4.2.0 and < 4.2.0.194 · >= 4.3.0 and < 4.3.0.105 · >= 4.4.0 and < 4.4.0.69 · >= 4.5.0 and < 4.5.0.54 · >= 4.6.0 and < 4.6.0.18
Fixed in: 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
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. UPGRADE to 4.0.0.390 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade api-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade api-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_4.0.0> sudo apt-mark hold api-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-manager sudo dnf downgrade api-manager-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add api-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 traffic manager UPGRADE
Affected: >= 4.5.0 and < 4.5.0.53 · >= 4.6.0 and < 4.6.0.18
Fixed in: 4.5.0.53, 4.6.0.18
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy traffic-manager || rpm -q traffic-manager || traffic-manager --version
2. UPGRADE to 4.5.0.53 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade traffic-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade traffic-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison traffic-manager sudo apt install traffic-manager=<VERSION_BEFORE_4.5.0> sudo apt-mark hold traffic-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list traffic-manager sudo dnf downgrade traffic-manager-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add traffic-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 universal gateway UPGRADE
Affected: >= 4.5.0 and < 4.5.0.54 · >= 4.6.0 and < 4.6.0.18
Fixed in: 4.5.0.54, 4.6.0.18
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy universal-gateway || rpm -q universal-gateway || universal-gateway --version
2. UPGRADE to 4.5.0.54 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade universal-gateway
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade universal-gateway
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison universal-gateway sudo apt install universal-gateway=<VERSION_BEFORE_4.5.0> sudo apt-mark hold universal-gateway
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list universal-gateway sudo dnf downgrade universal-gateway-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add universal-gateway
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-4249?

api control plane: upgrade to 4.5.0.55, 4.6.0.19; api manager: upgrade to 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; traffic manager: upgrade to 4.5.0.53, 4.6.0.18. Exact commands for each OS are on this page.

Is CVE-2026-4249 being exploited?

CVE-2026-4249 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-4249 affect?

CVE-2026-4249 affects api control plane, api manager, traffic manager. Severity is high (CVSS 8.6). 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

How urgent is CVE-2026-4249?

Priority 47/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.