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.
Sfruttata attivamente
- Nel catalogo CISA delle vulnerabilità sfruttate dal 24 set 2026
- Le agenzie federali statunitensi devono correggerla entro il 27 set 2026 (direttiva BOD 22-01)
- Primo attacco osservato 40 giorni dopo la divulgazione
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.
Fonte: CISA KEV · 24 set 2026 15 set 2026
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HProdotti coinvolti
| Vendor | Prodotto | Versioni |
|---|---|---|
| wso2 | api control plane | < 4.5.0.58 |
| wso2 | api manager | < 4.1.0.257 |
| wso2 | traffic manager | < 4.5.0.56 |
| wso2 | universal gateway | < 4.5.0.57 |
Articoli correlati
This product uses the NVD API but is not endorsed or certified by the NVD.