Threat intelligence · CVEs & news
Published: 08/06/2026 · Modified: 09/25/2026
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.
Requires: network access · Does not require: authentication, user interaction, special target conditions
Does not require: authentication, user interaction, special target conditions.
✓ Fix available in version 4.5.0.57; 4.6.0.21; 4.5.0.56; 4.5.0.58
Unauthorized access to the system, including potential compromise of administrative accounts and full account takeover.
Confidentiality: highIntegrity: highAvailability: high
Also affects components beyond the vulnerable one.
Community reports (unverified): exploitation 13 · PoC 6
The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.