AEGLIX vulnerability intelligence
CVE-2026-5430
CRITICAL · CVSS 10.0 · Analyzed
Published: 2026-08-06 · Updated: 2026-09-25 · Source: NVD
Vulnerability overview
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.
Severity and scoring
- CVSS score
- 10.0 · CRITICAL
- CVSS version
- 3.1
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Weaknesses
- CWE-347
CVSS measures technical severity; it does not establish whether this vulnerability is being exploited in your environment.
Known exploitation and remediation
Listed in CISA’s Known Exploited Vulnerabilities catalog.
- Affected product
- WSO2 · Multiple Products
- Added to catalog
- 2026-09-24
- 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.
- CISA remediation due date
- 2026-09-27
CISA deadlines apply to the organizations covered by its directives. Confirm your own remediation requirements.
Verify affected versions and patch availability in the vendor advisory before making changes.
Affected products and versions
cpe:2.3:a:wso2:api_control_plane:*:*:*:*:*:*:*:*
From (inclusive): 4.5.0
Before (exclusive): 4.5.0.58
cpe:2.3:a:wso2:api_control_plane:*:*:*:*:*:*:*:*
From (inclusive): 4.6.0
Before (exclusive): 4.6.0.22
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.1.0
Before (exclusive): 4.1.0.257
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.2.0
Before (exclusive): 4.2.0.197
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.3.0
Before (exclusive): 4.3.0.108
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.4.0
Before (exclusive): 4.4.0.72
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.5.0
Before (exclusive): 4.5.0.57
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.6.0
Before (exclusive): 4.6.0.21
cpe:2.3:a:wso2:traffic_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.5.0
Before (exclusive): 4.5.0.56
cpe:2.3:a:wso2:traffic_manager:*:*:*:*:*:*:*:*
From (inclusive): 4.6.0
Before (exclusive): 4.6.0.21
cpe:2.3:a:wso2:universal_gateway:*:*:*:*:*:*:*:*
From (inclusive): 4.5.0
Before (exclusive): 4.5.0.57
cpe:2.3:a:wso2:universal_gateway:*:*:*:*:*:*:*:*
From (inclusive): 4.6.0
Before (exclusive): 4.6.0.21
These are NVD CPE applicability entries. Some products depend on configuration conditions; consult the official record to confirm applicability.