CVE-2026-3416: The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create

Routine

MEDIUM 5.9REMOTEUPGRADEUPGRADE

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

The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's authenticity verification. Successful exploitation co

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-330
Published	2026-09-03
Last modified	2026-09-15

Publisher (CNA): WSO2 LLC · Vendor: wso2

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

Am I affected?

Timeline

2026-09-03 13:05 UTCPublished CVE record published
2026-09-15 18:02 UTCUpdated Record last modified

wso2 api control plane UPGRADE

Affected: >= 4.5.0 and < 4.5.0.53

Fixed in: 4.5.0.53

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.53 (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.1.0 and < 4.1.0.253 · >= 4.2.0 and < 4.2.0.193 · >= 4.3.0 and < 4.3.0.104 · >= 4.4.0 and < 4.4.0.68 · >= 4.5.0 and < 4.5.0.52

Fixed in: 4.1.0.253, 4.2.0.193, 4.3.0.104, 4.4.0.68, 4.5.0.52

Safe to downgrade to: a release before 4.1.0

1. Check installed version

apt-cache policy api-manager || rpm -q api-manager || api-manager --version

2. UPGRADE to 4.1.0.253 (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.1.0 (Debian / Ubuntu)

apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_4.1.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.1.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.

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-3416?

api control plane: upgrade to 4.5.0.53; api manager: upgrade to 4.1.0.253, 4.2.0.193, 4.3.0.104, 4.4.0.68, 4.5.0.52. Exact commands for each OS are on this page.

Is CVE-2026-3416 being exploited?

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

CVE-2026-3416 affects api control plane, api manager. Severity is medium (CVSS 5.9). The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a soph

How urgent is CVE-2026-3416?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-12737 HIGH 8.4 UPGRADE UPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu
CVE-2025-15039 CRITICAL 9.4 UPGRADE UPGRADE The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of a
CVE-2025-13394 MEDIUM 5.4 UPGRADE UPGRADE The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-
CVE-2026-5430 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE WSO2 Multiple Products Path Traversal Vulnerability
CVE-2024-8995 MEDIUM 4.9 UPGRADE UPGRADE Unused authorization codes issued to deleted users are not being properly invalidated or removed from the syst

References

← Back to latest CVEs