CVE-2026-29000GHSA-PM7G-W2CF-Q238
pac4j-jwt JwtAuthenticator Authentication Bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.5.9, 5.7.9, 6.3.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
pac4j-jwt versions prior to 4.5.9, 5.7.9, and 6.3.3 contain an authentication bypass vulnerability in JwtAuthenticator when processing encrypted JWTs that allows remote attackers to forge authentication tokens. Attackers who possess the server's RSA public key can create a JWE-wrapped PlainJWT with arbitrary subject and role claims, bypassing signature verification to authenticate as any user including administrators.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- pac4j pac4j-jwt
From 4.0 · fixed in 4.5.9; From 5.0 · fixed in 5.7.9; From 6.0 · fixed in 6.3.3
- org.pac4j:pac4j-jwtMaven
From 6.0.4.1 · fixed in 6.3.3
- org.pac4j:pac4j-jwtMaven
From 5.0.0-RC1 · fixed in 5.7.9
- org.pac4j:pac4j-jwtMaven
fixed in 4.5.9