CVE-2026-29000

CRITICALPre-NVD 9.110.0
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-05. A secondary CVSS source baseline 9.1; sources differ by 0.9.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-9505 (ENISA EUVD) · GHSA-pm7g-w2cf-q238 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 6.2%CVSS: 9.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
6.2%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
6.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 4, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available.
Web page

pac4j-jwt JwtAuthenticator Authentication Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pac4j-jwt-jwtauthenticator-authentication-bypass
Web page

Security advisory for pac4j-jwt (JwtAuthenticator) | pac4j

https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html
Web page

CVE-2026-29000: pac4j-jwt Auth Bypass PoC With a Public Key

https://www.codeant.ai/security-research/pac4j-jwt-authentication-bypass-public-key

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.pac4j:pac4j-jwt @ 6.3.3 (fixes >= 6.0.4.1, < 6.3.3)—ghsa
mavenorg.pac4j:pac4j-jwt @ 4.5.9 (fixes < 4.5.9)—ghsa
mavenorg.pac4j:pac4j-jwt @ 5.7.9 (fixes >= 5.0.0-RC1, < 5.7.9)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.pac4j:pac4j-jwt1.8.0 ... 4.5.8 (68 versions)
  • 6.0.4.1 up to 6.3.3: fixed in 6.3.3
  • 5.0.0-RC1 up to 5.7.9: fixed in 5.7.9
  • every version up to 4.5.9: fixed in 4.5.9
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 234 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 17:22 UTCEG score recompute
  2. 2026-11-01 17:21 UTCGHSA enrichmentGHSA-pm7g-w2cf-q238 · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  4. 2026-11-01 07:55 UTCGHSA enrichmentGHSA-pm7g-w2cf-q238 · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-01 07:55 UTCEG score recompute▲ 0.90
  6. 2026-10-31 17:02 UTCEG score recompute
  7. 2026-10-31 16:32 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  8. 2026-10-30 16:36 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  11. 2026-10-29 16:17 UTCEG score recompute
  12. 2026-10-28 16:32 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  13. 2026-10-28 15:58 UTCEG score recompute
  14. 2026-10-27 16:31 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  15. 2026-10-27 15:39 UTCEG score recompute
  16. 2026-10-26 15:16 UTCEG score recompute
  17. 2026-10-25 16:32 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  18. 2026-10-25 13:55 UTCEG score recompute
  19. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-24 13:36 UTCEG score recompute
  21. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-23 13:16 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-22 12:56 UTCEG score recompute
  25. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 70 more
  1. 2026-10-21 12:37 UTCEG score recompute
  2. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-20 12:10 UTCEG score recompute
  4. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-19 11:46 UTCEG score recompute
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-18 03:50 UTCEG score recompute
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-17 08:07 UTCEG score recompute
  10. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-16 07:46 UTCEG score recompute
  12. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-15 06:45 UTCEG score recompute
  14. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-14 02:27 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-12 22:40 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-12 16:16 UTCEG score recompute
  20. 2026-10-11 19:58 UTCEG score recompute
  21. 2026-10-11 17:12 UTCEG score recompute
  22. 2026-10-11 14:41 UTCEG score recompute
  23. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-10-08 16:42 UTCEG score recompute
  28. 2026-10-08 15:48 UTCEG score recompute
  29. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-20 20:15 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  40. 2026-09-19 20:33 UTCOSV refresh
  41. 2026-09-18 19:27 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  42. 2026-09-17 19:30 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  43. 2026-09-16 14:08 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  44. 2026-09-16 05:15 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  45. 2026-09-12 15:01 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  48. 2026-09-08 22:00 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  49. 2026-09-06 13:47 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  50. 2026-09-04 05:06 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  51. 2026-09-02 14:11 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  52. 2026-09-01 13:53 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  53. 2026-09-01 04:39 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  54. 2026-09-01 00:04 UTCOSV refresh
  55. 2026-08-30 19:17 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  57. 2026-08-28 21:41 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  58. 2026-08-27 14:25 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  59. 2026-08-26 14:46 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  60. 2026-08-25 13:49 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  61. 2026-08-24 14:17 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  62. 2026-08-23 00:19 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  63. 2026-08-21 23:49 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  64. 2026-08-20 22:55 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  65. 2026-08-19 17:03 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  66. 2026-08-18 13:48 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  67. 2026-08-16 14:56 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  68. 2026-08-16 02:14 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  69. 2026-08-15 01:30 UTCEPSS rescoreEPSS 5.9% · 92nd percentile
  70. 2026-08-14 08:33 UTCEG score recompute

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (7 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCtc4dy/CVE-2026-29000-PoC-Exploit
    Published May 12, 2026

    CVE-2026-29000 – pac4j-jwt Authentication Bypass (🔥 CVSS 10.0). One-click admin forge via public key JWE wrapping. Leaks configs, users, secrets. Keep-alive, proxy, custom JWKS.⚙️ Educational PoC Exploit tool.

    Open source ↗
  • GitHub PoCSTK-Security/CVE-2026-29000-pac4j-jwt
    Published May 3, 2026

    CVE-2026-29000 PoC: pac4j-jwt PlainJWT-in-JWE authentication bypass.

    Open source ↗
  • GitHub PoCstrikoder/CVE-2026-29000-pac4j-jwt
    Published May 3, 2026

    CVE-2026-29000 PoC: pac4j-jwt PlainJWT-in-JWE authentication bypass.

    Open source ↗
  • GitHub PoCStrikoder-Premium/CVE-2026-29000-pac4j-jwt
    Published May 3, 2026

    CVE-2026-29000 PoC: pac4j-jwt PlainJWT-in-JWE authentication bypass.

    Open source ↗
  • GitHub PoCRootX111/cve-2026-29000
    Published Mar 16, 2026

    cve-2026-29000 exploit

    Open source ↗
  • GitHub PoCalihussainzada/CVE-2026-29000-Python-PoC-pac4j-JWT-AuthenticationBypass-Poc
    Published Mar 13, 2026
    Open source ↗
  • GitHub PoCkernelzeroday/CVE-2026-29000
    Published Mar 5, 2026

    pac4j-jwt JwtAuthenticator auth bypass (CVE-2026-29000) writeup and PoCs

    Open source ↗

Frequently asked(5)

What is CVE-2026-29000?
CVE-2026-29000 is a critical-severity vulnerability; its CVE record was published on March 4, 2026. 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…
When was the CVE record for CVE-2026-29000 published?
The CVE record for CVE-2026-29000 was published on March 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-29000 actively exploited?
CVE-2026-29000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.2% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29000?
CVE-2026-29000 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2026-29000?
A fix for CVE-2026-29000 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29000

Explore →

Is Your Infrastructure Affected by CVE-2026-29000?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.