CVE-2026-29000Public exploitNetwork attack vector

Authentication bypass via unsigned JWE payload acceptance

Published Mar 4, 2026 · Updated Mar 4, 2026

Authentication bypass in pac4j-jwt before 4.5.9, 5.7.9, or 6.3.3 allows remote attackers to forge tokens through encrypted JWTs. JwtAuthenticator accepts a decrypted PlainJWT when toSignedJWT returns null, skips its signature-verification block, and creates a profile from unverified claims. Exploitation requires RSA-based JWE processing, the server's public key, and attacker-selected claims, granting authentication as any represented user or role.

CVSS severity9.3
Critical
EPSS probability5.86%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in pac4j-jwt before 4.5.9, 5.7.9, or 6.3.3 allows remote attackers to forge tokens through encrypted JWTs. JwtAuthenticator accepts a decrypted PlainJWT when toSignedJWT returns null, skips its signature-verification block, and creates a profile from unverified claims. Exploitation requires RSA-based JWE processing, the server's public key, and attacker-selected claims, granting authentication as any represented user or role.

The record

CVE
CVE-2026-29000
Published
Mar 4, 2026
Updated
Mar 4, 2026
Vendor
pac4j
Product
pac4j-jwt
Classifications
CWE-347, T1606
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 4, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 4, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.0 <4.5.9
  2. Affected versionversion=5.0 <5.7.9
  3. Affected versionversion=6.0 <6.3.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

pac4j · pac4j-jwtversion=4.0 <4.5.9; version=5.0 <5.7.9; version=6.0 <6.3.3

Published CVSS scores

10.0GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
9.3VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1606Forge Web Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo