Appsecure logo

CVE-2026-29000: Critical Vulnerability in pac4j-jwt

CVE-2026-29000 represents a critical authentication bypass vulnerability in pac4j-jwt. Attackers can exploit this vulnerability to forge authentication tokens, allowing unauthorized access to sensitive systems. Immediate action is required to mitigate risks associated with this vulnerability.

CRITICALPublic ExploitCVSS 9.3 · Published March 4, 2026

Not a customer? See how AppSecure simulates real world attacks to protect your infrastructure.

Speak to Experts

CVE-2026-29000 is a critical vulnerability affecting pac4j-jwt versions prior to 4.5.9, 5.7.9, and 6.3.3. This vulnerability allows remote attackers to bypass authentication through the JwtAuthenticator when processing encrypted JWTs, posing significant risks for organizations. The vulnerability is classified as critical with a CVSS score of 9.3, indicating a high severity level due to its potential impact on confidentiality and integrity.

The risk to organizations includes unauthorized access to sensitive user accounts, including those of administrators, due to forged authentication tokens. Attackers who possess the server's RSA public key can create a JWE-wrapped PlainJWT with arbitrary subject and role claims, thus bypassing signature verification. Given the widespread use of JWTs in modern applications, the implications of this vulnerability are far-reaching.

Organizations should prioritize patching immediately to address this vulnerability. The urgency is underscored by the simplicity with which attackers can exploit it, coupled with the absence of user interaction and privilege requirements.

As of now, the exploitation status is confirmed with proof of concept (PoC) available in multiple GitHub repositories. Organizations are advised to monitor their systems closely and implement the necessary patches as soon as they become available.

Vulnerability Details

The official description of this vulnerability states that pac4j-jwt versions before 4.5.9, 5.7.9, and 6.3.3 contain an authentication bypass vulnerability in JwtAuthenticator when processing encrypted JWTs. This vulnerability allows remote attackers to forge authentication tokens, compromising the security of affected applications.

The identified CVSS base score of 9.3 confirms the critical nature of this vulnerability, with a high confidentiality and integrity impact but no availability impact. The vulnerability is classified under CWE-347, indicating a failure to enforce authentication.

Technical Analysis

The root cause of this vulnerability lies in the improper handling of encrypted JWTs by the JwtAuthenticator. Attackers can exploit this flaw via a network attack vector, as the attack complexity is low and does not require any privileges or user interaction. The potential for confidentiality and integrity impacts makes this vulnerability particularly dangerous.

Given the requirements for exploitation, an attacker only needs access to the server's RSA public key. This low barrier to entry significantly increases the risk of exploitation, especially in environments where sensitive information is handled.

Risk & Impact Analysis

Real-world deployment of vulnerable versions poses a substantial risk to organizations. The ability for attackers to authenticate as any user, including those with administrative privileges, implies a high potential for data breaches and unauthorized actions within applications.

Organizations must understand the urgency of addressing this vulnerability in their patch management cycles, particularly due to the critical CVSS score. The implications of an unpatched system could lead to significant operational disruptions and data compromise.

Exploitation Status

Signal

Status

Known Exploit

Yes

Public PoC

Yes

Actively Exploited

No

Ransomware Use

No

Affected Versions

The affected versions include all versions of pac4j-jwt prior to 4.5.9, 5.7.9, and 6.3.3. Organizations running these versions are at risk and should take immediate action to remediate.

Mitigation & Remediation

Organizations should prioritize upgrading to the latest versions of pac4j-jwt—specifically, versions 4.5.9, 5.7.9, or 6.3.3—to mitigate this vulnerability. If an immediate upgrade is not feasible, consider implementing alternative security measures such as robust network controls and continuous monitoring of authentication logs to detect any unauthorized access attempts.

For more information on effective security practices, organizations can consult our guide on penetration testing methodology and enhance their security posture.

Detection Guidance

To detect potential exploitation of this vulnerability, organizations should monitor for abnormal authentication patterns, including unexpected user roles and claims in JWT tokens. Additionally, logging and analyzing authentication attempts can help identify anomalous behaviors indicative of an ongoing attack.

AppSecure Threat Intelligence Insight

CVE-2026-29000 highlights a critical flaw in the authentication process of pac4j-jwt that organizations must address promptly. This vulnerability serves as a reminder of the importance of rigorous security testing in software development. Security teams are encouraged to review their authentication mechanisms and ensure they are not susceptible to similar bypass vulnerabilities. For further insights, organizations may refer to our resources on penetration testing best practices and vulnerability management programs to strengthen their defenses against future threats.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Latest CVEs. Recently published vulnerabilities from the NVD database.

View all vulnerabilities
CVE IDSeverity
CVE-2025-65418HIGH
CVE-2025-65417MEDIUM
CVE-2025-65416MEDIUM
CVE-2025-65415MEDIUM
CVE-2025-61314HIGH

Protect Your Business with Hacker-Focused Approach.