Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-8325: The software fails to enforce role-based access controls for certain Gateway API invocations

24
Routine
MEDIUM 6.3UPGRADEUPGRADEUPGRADE

CVE-2025-8325 is a medium-severity flaw (CVSS 6.3) 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 software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal Service APIs, potentially exposing them in WSO2 APIM 3.x versions. A malicious actor with a valid user account on a vulnerable deployment can perform sensitive operations against the Gateway REST API regardle

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 93%)
CISA exploited listNo
WeaknessCWE-281
Published2026-05-11
Last modified2026-10-14
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

Last updated 2026-10-14 · 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.18
Fixed in: 4.5.0.18
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.18 (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: >= 3.2.0 and < 3.2.0.435 · >= 3.2.1 and < 3.2.1.55 · >= 4.0.0 and < 4.0.0.355 · >= 4.1.0 and < 4.1.0.219 · >= 4.2.0 and < 4.2.0.157 · >= 4.3.0 and < 4.3.0.70 · >= 4.4.0 and < 4.4.0.33 · >= 4.5.0 and < 4.5.0.17
Fixed in: 3.2.0.435, 3.2.1.55, 4.0.0.355, 4.1.0.219, 4.2.0.157, 4.3.0.70, 4.4.0.33, 4.5.0.17
Safe to downgrade to: a release before 3.2.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. UPGRADE to 3.2.0.435 (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 3.2.0 (Debian / Ubuntu)
apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_3.2.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_3.2.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.17
Fixed in: 4.5.0.17
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.17 (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.17
Fixed in: 4.5.0.17
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.17 (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-2025-8325?

api control plane: upgrade to 4.5.0.18; api manager: upgrade to 3.2.0.435, 3.2.1.55, 4.0.0.355, 4.1.0.219, 4.2.0.157, 4.3.0.70, 4.4.0.33, 4.5.0.17; traffic manager: upgrade to 4.5.0.17. Exact commands for each OS are on this page.

Is CVE-2025-8325 being exploited?

CVE-2025-8325 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-2025-8325 affect?

CVE-2025-8325 affects api control plane, api manager, traffic manager. Severity is medium (CVSS 6.3). The software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal

How urgent is CVE-2025-8325?

Priority 24/100. No elevated risk signals yet.

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.