CVE-2026-5430
Vulnerability Summary
Timeline
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.
CVSS Metrics
- v3.1•CRITICAL•Score: 10CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Trends
Current EPSS score: 0.37%• Percentile: 29%
Techniques & Countermeasures
- CWE-347•Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Affected Systems
- wso2•api_control_plane
≥ 4.5.0, < 4.5.0.58 | ≥ 4.6.0, < 4.6.0.22
- wso2•api_manager
≥ 4.1.0, < 4.1.0.257 | ≥ 4.2.0, < 4.2.0.197 | ≥ 4.3.0, < 4.3.0.108 | ≥ 4.4.0, < 4.4.0.72 | ≥ 4.5.0, < 4.5.0.57 | ≥ 4.6.0, < 4.6.0.21
- wso2•traffic_manager
≥ 4.5.0, < 4.5.0.56 | ≥ 4.6.0, < 4.6.0.21
- wso2•universal_gateway
≥ 4.5.0, < 4.5.0.57 | ≥ 4.6.0, < 4.6.0.21
- wso2•wso2 api control plane
≥ 4.5.0, < 4.5.0.58 | ≥ 4.6.0, < 4.6.0.22
- wso2•wso2 api manager
≥ 4.1.0, < 4.1.0.257 | ≥ 4.2.0, < 4.2.0.197 | ≥ 4.3.0, < 4.3.0.108 | ≥ 4.4.0, < 4.4.0.72 | ≥ 4.5.0, < 4.5.0.57 | ≥ 4.6.0, < 4.6.0.21
- wso2•wso2 carbon api manager rest api utility
≥ 9.20.74, < 9.20.74.401 | ≥ 9.28.116, < 9.28.116.417 | ≥ 9.29.120, < 9.29.120.236 | ≥ 9.30.67, < 9.30.67.167 | ≥ 9.31.86, < 9.31.86.158 | ≥ 9.32.147, < 9.32.147.59
- wso2•wso2 traffic manager
≥ 4.5.0, < 4.5.0.56 | ≥ 4.6.0, < 4.6.0.21
- wso2•wso2 universal gateway
≥ 4.5.0, < 4.5.0.57 | ≥ 4.6.0, < 4.6.0.21