How severe is GHSA-pm7g-w2cf-q238?

GHSA-pm7g-w2cf-q238 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-pm7g-w2cf-q238?

GHSA-pm7g-w2cf-q238 affects the following packages: org.pac4j:pac4j-jwt (Maven), org.pac4j:pac4j-jwt (Maven), org.pac4j:pac4j-jwt (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pm7g-w2cf-q238?

Update org.pac4j:pac4j-jwt to 6.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pm7g-w2cf-q238 is resolved across your whole dependency graph.

How do I detect GHSA-pm7g-w2cf-q238 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.pac4j:pac4j-jwt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-pm7g-w2cf-q238 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pm7g-w2cf-q238?

O3 pinpoints whether GHSA-pm7g-w2cf-q238 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-pm7g-w2cf-q238 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-pm7g-w2cf-q238, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-pm7g-w2cf-q238?

GHSA-pm7g-w2cf-q238 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pm7g-w2cf-q238 published, and has it been updated?

GHSA-pm7g-w2cf-q238 was published on March 5, 2026 and was last updated on March 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-pm7g-w2cf-q238

CRITICAL

GHSA-pm7g-w2cf-q238 is a critical-severity (CVSS 10) CWE-347 vulnerability in org.pac4j:pac4j-jwt. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-pm7g-w2cf-q238 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

pac4j-jwt: JwtAuthenticator Authentication Bypass via JWE-Wrapped PlainJWT

Also known asCVE-2026-29000

Published

Mar 5, 2026

Updated

Mar 6, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Mar 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

☕org.pac4j:pac4j-jwt☕org.pac4j:pac4j-jwt☕org.pac4j:pac4j-jwt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.pac4j:pac4j-jwt`	≥ 6.0.4.1&&< 6.3.3	6.3.3
☕Maven	`org.pac4j:pac4j-jwt`	≥ 5.0.0-RC1&&< 5.7.9	5.7.9
☕Maven	`org.pac4j:pac4j-jwt`	all versions	4.5.9

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

tc4dy/CVE-2026-29000-PoC-Exploit

CVE-2026-29000 – pac4j-jwt Authentication Bypass (🔥 CVSS 10.0). One-cli

⭐ 3🍴 0Jun 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.pac4j:pac4j-jwt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.pac4j:pac4j-jwt to 6.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pm7g-w2cf-q238 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pm7g-w2cf-q238 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pm7g-w2cf-q238. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-pm7g-w2cf-q238 in your dependencies?

O3 detects GHSA-pm7g-w2cf-q238 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works