Skip to main content
ExploitedIn CISA KEVFix available

CVE-2026-5430

Exploitation confirmed. First attested on 2026-09-16 by CISA-ADP, CISA KEV, GCVE · previdian.

  • Published2026-08-06
  • Fixed in4.6.0.21 · 4.5.0.57 · 4.4.0.72 · 4.3.0.108 · 4.2.0.197 · 4.1.0.257
  • WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access. Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.

Timeline

dates in UTC
  1. 2026-08-0608:16CVE publishedNVD
  2. 2026-09-1605:18Listed as exploited by GCVEGCVE
  3. 2026-09-1605:18Exploitation first reportedGCVE
  4. 2026-09-24Added to the CISA KEV catalogCISA KEV
  5. 2026-09-2419:40SSVC exploitation set to activeCISA-ADP
  6. 2026-10-2523:12EPSS crossed 10 %FIRST EPSS

Versions per branch

NVD
Wso2 api manager
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.0.214.6.0.21
4.5≥ 4.5.0, < 4.5.0.574.5.0.57
4.4≥ 4.4.0, < 4.4.0.724.4.0.72
4.3≥ 4.3.0, < 4.3.0.1084.3.0.108
4.2≥ 4.2.0, < 4.2.0.1974.2.0.197
4.1≥ 4.1.0, < 4.1.0.2574.1.0.257
Wso2 api control plane
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.0.224.6.0.22
4.5≥ 4.5.0, < 4.5.0.584.5.0.58
Wso2 traffic manager
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.0.214.6.0.21
4.5≥ 4.5.0, < 4.5.0.564.5.0.56

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA5 products

As WSO2, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • WSO2 Universal Gatewayother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.57fixed in 4.5.0.57custom
    • ≥ 4.6.0, < 4.6.0.21fixed in 4.6.0.21custom
  • WSO2 Traffic Managerother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.56fixed in 4.5.0.56custom
    • ≥ 4.6.0, < 4.6.0.21fixed in 4.6.0.21custom
  • WSO2 API Control Planeother versions: not affected
    Affected
    • ≥ 4.5.0, < 4.5.0.58fixed in 4.5.0.58custom
    • ≥ 4.6.0, < 4.6.0.22fixed in 4.6.0.22custom
  • WSO2 API Managerother versions: not affected
    Affected
    • ≥ 4.1.0, < 4.1.0.257fixed in 4.1.0.257custom
    • ≥ 4.2.0, < 4.2.0.197fixed in 4.2.0.197custom
    • ≥ 4.3.0, < 4.3.0.108fixed in 4.3.0.108custom
    • ≥ 4.4.0, < 4.4.0.72fixed in 4.4.0.72custom
    • ≥ 4.5.0, < 4.5.0.57fixed in 4.5.0.57custom
    • ≥ 4.6.0, < 4.6.0.21fixed in 4.6.0.21custom

    Not affected < 4.1.0 (status unknown)

  • WSO2 Carbon API Manager Rest API Utilityother versions: unknown

    package org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.util

    Affected
    • ≥ 9.20.74, < 9.20.74.401fixed in 9.20.74.401custom
    • ≥ 9.28.116, < 9.28.116.417fixed in 9.28.116.417custom
    • ≥ 9.29.120, < 9.29.120.236fixed in 9.29.120.236custom
    • ≥ 9.30.67, < 9.30.67.167fixed in 9.30.67.167custom
    • ≥ 9.31.86, < 9.31.86.158fixed in 9.31.86.158custom
    • ≥ 9.32.147, < 9.32.147.59fixed in 9.32.147.59custom

    Not affected ≥ 9.33.106

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-08-06

Fix

  1. Update Wso2 api manager to 4.6.0.21 · 4.5.0.57 · 4.4.0.72 · 4.3.0.108 · 4.2.0.197 · 4.1.0.257
  2. CISA’s required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.due 2026-09-27

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2026-09-24
Patch Due Date
2026-09-27
Ransomware Use
Unknown
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Published
2026-08-06
Last Modified
2026-09-25
NVD status
Analyzed
GitHub Advisory
GHSA-j7vh-5w8q-4m4x

Frequently asked questions

What is CVE-2026-5430?

The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access. Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.

Is CVE-2026-5430 actively exploited?

Yes. CVE-2026-5430 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-09-27.

What is the CVSS score for CVE-2026-5430?

CVE-2026-5430 has a CVSS v3 base score of 10 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, September 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record