CVE-2026-29000
A public proof of concept exists; no exploitation attested.
- Published2026-03-04
- Fixed in6.3.3 · 5.7.9 · 4.5.9
- WeaknessCWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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
dates in UTC- 2026-03-0422:16CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-25 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-29000?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-29000?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.0.4.1, < 6.3.3 | 6.3.3 | OSV |
| 5.x | ≥ 5.0.0-RC1, < 5.7.9 | 5.7.9 | OSV |
| 4.5 | < 4.5.9 | 4.5.9 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update pac4j-jwt to 6.3.3 · 5.7.9 · 4.5.9
Detection
read 2026-10-25 00:28 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 20 repositories, unverifiedkernelzeroday/CVE-2026-29000rootdirective-sec/CVE-2026-29000-Labmanbahadurthapa1248/CVE-2026-29000---pac4j-jwt-Authentication-Bypass-PoCCrims-on/CVE-2026-29000alihussainzada/CVE-2026-29000-Python-PoC-pac4j-JWT-AuthenticationBypass-Poc PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionpoc2026-03-07
- OpenCVESSVC decisionpoc—
- CNACVSS 4.09.3read 2026-10-23
- CNACVSS 3.19.1read 2026-10-23
- CNAweakness (CWE)CWE-347read 2026-10-23
- FIRST EPSSEPSS score6.1 %2026-10-25
- PoC-in-GitHubproof of concept20read 2026-10-25
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-03-04
- Last Modified
- 2026-10-08
- NVD status
- Deferred
Frequently asked questions
What is CVE-2026-29000?
Is CVE-2026-29000 actively exploited?
What is the CVSS score for CVE-2026-29000?
Running pac4j-jwt? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.