Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-1728: Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access pro

50
This month
CRITICAL 9.8REMOTEUPGRADEUPGRADEUPGRADE

CVE-2026-1728 is a critical-severity flaw (CVSS 9.8) 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.

Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2 products, potentially leading to full administrative account takeover. This requires the attacker to already possess a low-privileged user account and be able to obtain a valid token for it.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 59%)
CISA exploited listNo
WeaknessCWE-269
Published2026-08-06
Last modified2026-08-10
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

Last updated 2026-08-10 · 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.49 · >= 4.6.0 and < 4.6.0.13
Fixed in: 4.5.0.49, 4.6.0.13
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.49 (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.384 · >= 4.1.0 and < 4.1.0.248 · >= 4.2.0 and < 4.2.0.188 · >= 4.3.0 and < 4.3.0.99 · >= 4.4.0 and < 4.4.0.63 · >= 4.5.0 and < 4.5.0.48 · >= 4.6.0 and < 4.6.0.12
Fixed in: 4.0.0.384, 4.1.0.248, 4.2.0.188, 4.3.0.99, 4.4.0.63, 4.5.0.48, 4.6.0.12
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.384 (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.47 · >= 4.6.0 and < 4.6.0.12
Fixed in: 4.5.0.47, 4.6.0.12
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.47 (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.48 · >= 4.6.0 and < 4.6.0.12
Fixed in: 4.5.0.48, 4.6.0.12
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.48 (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-1728?

api control plane: upgrade to 4.5.0.49, 4.6.0.13; api manager: upgrade to 4.0.0.384, 4.1.0.248, 4.2.0.188, 4.3.0.99, 4.4.0.63, 4.5.0.48, 4.6.0.12; traffic manager: upgrade to 4.5.0.47, 4.6.0.12. Exact commands for each OS are on this page.

Is CVE-2026-1728 being exploited?

CVE-2026-1728 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-1728 affect?

CVE-2026-1728 affects api control plane, api manager, traffic manager. Severity is critical (CVSS 9.8). Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2

How urgent is CVE-2026-1728?

Priority 50/100. Critical 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.