Widely used auth library; token forgery permits admin impersonation across apps.
CVE-2026-29000
Auth bypass: forge JWE-wrapped PlainJWT to impersonate users.
Is CVE-2026-29000 being exploited?
Not confirmed. CVE-2026-29000 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 5.9% probability of exploitation in the next 30 days.
How severe is CVE-2026-29000?
CVE-2026-29000 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-29000?
Yes. A fix has been recorded for CVE-2026-29000. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-29000 affect?
CVE-2026-29000 affects pac4j-jwt <= 4.5.9, <= 5.7.9, <= 6.3.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-29000?
Upgrade to fixed versions: 4.5.9+, 5.7.9+, or 6.3.3+.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can forge tokens using the server's RSA key to bypass verification and impersonate admins.
Immediate action required
- affected>= 4.0 and < 4.5.9
- affected>= 5.0 and < 5.7.9
- affected>= 6.0 and < 6.3.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.