Skip to content

CVE-2026-5430: WSO2 API Manager JWT Signature Validation Bypass and Account Takeover

Density:
HERMES

HERMES THREAT SCORE & ENTERPRISE RISK EXPOSURE

Target: Enterprise API Gateways, Identity Brokering & Cloud Control Planes
Confidence: 96%
96 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 19 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 evaluates CVE-2026-5430 at 9.8 to 10.0 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Hermes Threat Score calculates 96 (CRITICAL). Traditional metrics treat API gateways as generic web proxies; however, WSO2 API Manager acts as the identity-brokering perimeter nexus for enterprise microservices, cloud integrations, and autonomous AI tool routing. Unauthenticated signature validation bypass permits adversaries to mint valid tokens for any tenant (including carbon.super), weaponize active in-the-wild exploitation (CISA KEV), extract sensitive upstream authorization keys, and re-route core business traffic.

HASS

HASS AGENTIC SEVERITY & PERIMETER BOUNDARY IMPACT

Target: WSO2 API Manager & Universal Gateway Token Validation Engine
Confidence: 92%
88 / 100
CRITICAL

Measures specific systemic risk arising from autonomy, tool authority, and cascading execution.

Dimension Breakdown
Autonomy 18 / 20
Tool Access 19 / 20
Privilege 14 / 15
Persistence 13 / 15
External Impact 14 / 15
Propagation 10 / 15
โš–๏ธ Divergence & Operational Rationale

Autonomous agents and AI-driven workflow engines depend on centralized API gateways to discover tools, validate bearer credentials, and route outbound LLM actions. A complete authentication bypass at the gateway level allows attackers to forge agent credentials, intercept inter-agent tool invocations, hijack data pipelines, and inject deceptive responses directly into autonomous model decision loops.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-5430: WSO2 API Manager JWT Signature Validation Bypass and Account TakeoverVULNERABILITY

Connected Nodes: 3
Active Relationships (Outgoing)
→ affectsPRODUCTOracle MySQL Server & Database Engine
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Oracle MySQL Server & Database Engine documented in Hermes dossier.”

Supporting Verified Evidence:
→ exploitsAGENTIC ATTACK_PATTERNAAP-006: Inter-Agent Semantic Message Spoofing
92% VERY_HIGH

Exploitation of unauthenticated, unsigned inter-agent communication channels to forge delegation directives, impersonate orchestrator agents, and command worker subagents.

๐Ÿ” Why is this related? (Evidence & Provenance)

“CVE-2026-5430 weaponizes the agentic attack pattern formalized under AAP-006.”

Supporting Verified Evidence:
→ exploitsAGENTIC ATTACK_PATTERNAAP-007: Autonomous Cascading RCE
92% VERY_HIGH

Cascading multi-stage attack chaining context injection, autonomous loop planning, and un-sandboxed execution sinks to achieve persistent root shell compromise on host machines.

๐Ÿ” Why is this related? (Evidence & Provenance)

“CVE-2026-5430 weaponizes the agentic attack pattern formalized under AAP-007.”

Supporting Verified Evidence:

The WSO2 API Manager suite relies on a modular architecture where the Control Plane coordinates with Traffic Managers, Key Managers, and Universal Gateways to enforce policy boundaries.

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-5430CISA KEV Exploited Entry / WSO2 Security Advisory
Vulnerability ClassImproper Authentication (CWE-287) / Signature Bypass (CWE-347)Complete bypass of gateway identity validation
Vulnerable Componentorg.wso2.carbon.identity.oauth / Gateway JWT HandlerUnchecked signature algorithm resolution
Exploitation VectorCrafted HTTP request with forged JWT Bearer authorizationAdministrative portal and backend API takeover
Privileges RequiredNone (PR:N)Unauthenticated remote access
Privileges ObtainedSuper-Tenant Administrator (carbon.super / admin)Full control of API gateways, proxies, and keys
Affected VersionsWSO2 API Manager 4.1.0 to 4.6.0; Universal Gateway 4.5.0, 4.6.0Enterprise API gateways, hybrid cloud routing
Fixed UpdatesWSO2 Security Update May 2026 / 4.6.0-HFStrict algorithm allowlisting and cryptographic validation

In WSO2 API Manager, incoming requests bearing JWT tokens are processed by internal authenticator classes. Under vulnerable versions, the signature verification routine dynamically parsed the algorithm specified in the JWT header (alg) without validating it against an immutable server-side allowlist:

// Vulnerable JWT Verification Routine (Pre-Patch Concept)
public boolean validateToken(SignedJWT signedJWT) throws SecurityException {
JWSHeader header = signedJWT.getHeader();
JWSAlgorithm algorithm = header.getAlgorithm();
// FLAW: If algorithm is not recognized or belongs to an unsupported class,
// the verification dispatcher fails open or branches into an unauthenticated state
// rather than rejecting the token outright.
JWSVerifier verifier = JWSVerifierFactory.getVerifier(algorithm);
if (verifier == null) {
log.warn("Unsupported JWT signing algorithm: " + algorithm.getName());
// Defect: parser returns true or falls through to claim extraction without cryptographic proof!
return true;
}
return signedJWT.verify(verifier);
}

When an attacker crafts a JWT header with an unsupported algorithm identifier or manipulates the signing structure, the parser encounters an edge case where the lack of an applicable cryptographic verifier fails to trigger an immediate 401 Unauthorized rejection. Instead, the downstream authentication filter receives an extracted JWTClaimsSet and treats the identity claims as authenticated.

Once signature checking is bypassed, the attacker inserts administrative claims into the JWT payload:

{
"sub": "admin@wso2.com",
"http://wso2.org/claims/role": ["admin", "Internal/everyone"],
"http://wso2.org/claims/tenant": "carbon.super",
"iss": "https://localhost:9443/oauth2/token",
"exp": 1893456000
}

The gateway accepts these claims, granting the attacker unauthenticated access to the Management Console (/carbon), the API Publisher portal (/publisher), and internal configuration endpoints.


sequenceDiagram
autonumber
actor Attacker as Threat Actor (Internet / External)
participant GW as WSO2 Universal Gateway / Control Plane
participant Auth as JWT Validation Filter
participant Backend as Enterprise Backend Services & AI APIs
Attacker->>GW: POST /api/am/publisher/v3/apis (Header: Bearer <Forged_JWT>)
GW->>Auth: Pass token for cryptographic signature check
Auth-->>Auth: Inspect 'alg' header -> unsupported algorithm encountered
Auth-->>Auth: Verification fails open (signature check bypassed)
Auth->>GW: Return valid ClaimsSet (sub: admin, tenant: carbon.super)
GW->>Attacker: 200 OK (Full Publisher API Access)
Attacker->>GW: Modify API endpoints / export client secrets & API keys
GW->>Backend: Forward malicious queries / intercept production payload flows
  1. Token Forgery: The adversary generates an unsigned or malformed JWT containing administrative claims (sub: admin, carbon.super) and sets the header alg to an unsupported algorithm string.
  2. Gateway Dispatch: The attacker submits an HTTP request to the WSO2 API Manager Control Plane or API Publisher endpoint with the forged Bearer token.
  3. Bypass Trigger: The gatewayโ€™s token processor fails to match the algorithm with an approved validator, skipping cryptographic verification and accepting the forged payload.
  4. Administrative Escalation: The attacker assumes the highest privilege tier (carbon.super administrator), gaining visibility into all configured APIs, rate-limits, and upstream endpoint credentials.
  5. Lateral Pivot & Interception: The adversary reconfigures API routing targets to point to an external proxy, intercepting upstream enterprise traffic and harvesting confidential tokens.

DFIR teams auditing WSO2 deployments should immediately inspect gateway and access logs for forged token artifacts and anomalous administrative actions:

Terminal window
# 1. Search WSO2 audit logs for anomalous logins or tenant switching
grep -E "carbon.super.*admin" /var/log/wso2/audit.log | grep -v "127.0.0.1"
# 2. Inspect HTTP access logs for unusual JWT headers or requests to management APIs
grep -E "(POST|PUT) /api/am/publisher" /var/log/wso2/http_access.log | awk '{print $1, $4, $7, $9}'
# 3. Check for recently created or altered API definitions
find /opt/wso2/repository/deployment/server/synapse-configs/ -type f -mtime -5 -ls
# 4. Extract active listening ports and established connections on the API Control Plane
ss -tulpn | grep -E "9443|9763|8243|8280"
ss -tan state established '( dport = :9443 or sport = :9443 )'
# 5. Check for unauthorized administrative users in local H2 or external MySQL databases
grep -i "insert into um_user" /var/log/wso2/wso2carbon.log

title: WSO2 API Manager Authentication Bypass Attempt
id: 5430c01-wso2-jwt-auth-bypass
status: experimental
description: Detects HTTP requests to WSO2 API Manager management endpoints with malformed or unsupported JWT algorithm headers indicative of CVE-2026-5430 exploitation.
author: Hermes Codex Detection Engineering
date: 2026-09-25
logsource:
category: webserver
product: wso2
detection:
selection_path:
cs-method:
- 'POST'
- 'PUT'
- 'DELETE'
- 'GET'
cs-uri-stem|startswith:
- '/api/am/publisher'
- '/api/am/admin'
- '/carbon/'
selection_status:
sc-status: 200
filter_known_ip:
c-ip:
- '10.0.0.0/8'
- '172.16.0.0/12'
- '192.168.0.0/16'
condition: selection_path and selection_status and not filter_known_ip
falsepositives:
- Legitimate automated CI/CD deployment pipelines calling publisher APIs from external runner IPs.
level: critical
tags:
- attack.initial_access
- attack.t1190
- attack.defense_evasion
- attack.t1550.001
- cve.2026-5430

Upgrade all instances of WSO2 API Manager, Control Plane, and Universal Gateway to patched releases immediately:

  • Apply the WSO2 May 2026 Security Update or upgrade to version 4.6.0 with latest service pack.
  • Enforce strict asymmetric algorithm pinning (RS256 or ES256) in deployment.toml:
[oauth.jwt]
enable_signature_verification = true
allowed_algorithms = ["RS256", "ES256"]
reject_unsupported_algorithms = true
  1. Rotate All Client Secrets: Invalidate and re-issue all consumer keys and application secrets registered in the Developer Portal.
  2. Purge Token Caches: Clear gateway memory caches and distributed Redis/Hazelcast token stores to prevent replay of forged session entries.
  3. Network Boundary Isolation: Restrict access to port 9443 (Management Console) and port 9763 to internal bastion hosts and administrative VPNs.