Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-5430 – JWT Authentication Bypass – WSO2 API Manager 4.1.0–4.6.0 and related platform compon

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-5430 is a critical JWT authentication bypass affecting WSO2 API Manager and several related WSO2 API platform components. JWT authentication can be bypassed when a token is signed using an unsupported algorithm, allowing an unauthenticated remote attacker to gain unauthorized access. It carries a CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: JWT validation logic fails to properly reject tokens signed with unsupported cryptographic algorithms, classified as CWE-347 (Improper Verification of Cryptographic Signature).
  • Trigger conditions: An attacker crafts and submits a JWT signed with an unsupported algorithm that the validation routine accepts instead of rejecting.
  • Attack vector: Network-based, low attack complexity, no privileges and no user interaction required.
  • Impact: Bypass of JWT authentication leading to unauthorized access, with high impact to confidentiality, integrity, and availability.

Affected software

  • WSO2 API Manager: 4.1.0 before 4.1.0.257; 4.2.0 before 4.2.0.197; 4.3.0 before 4.3.0.108; 4.4.0 before 4.4.0.72; 4.5.0 before 4.5.0.57; 4.6.0 before 4.6.0.21
  • WSO2 Universal Gateway: 4.5.0 before 4.5.0.57; 4.6.0 before 4.6.0.21
  • WSO2 Traffic Manager: 4.5.0 before 4.5.0.56; 4.6.0 before 4.6.0.21
  • WSO2 API Control Plane: 4.5.0 before 4.5.0.58; 4.6.0 before 4.6.0.22

Severity

  • CVSS v3.1 base score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Apply the fixed update levels per the WSO2 security advisory — WSO2 API Manager 4.1.0.257 / 4.2.0.197 / 4.3.0.108 / 4.4.0.72 / 4.5.0.57 / 4.6.0.21; Universal Gateway 4.5.0.57 / 4.6.0.21; Traffic Manager 4.5.0.56 / 4.6.0.21; API Control Plane 4.5.0.58 / 4.6.0.22. Support subscribers should update via WSO2 Updates; open-source users should upgrade to unaffected versions.
  • If no patch: Follow the mitigation guidance in the official WSO2 security advisory and restrict network access to affected management and gateway interfaces.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: WSO2 API Manager
  • Server response header: WSO2 Carbon Server

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge