Is CVE-2026-82462 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82462 being exploited in the wild.

How severe is CVE-2026-82462?

Medium severity, with a CVSS score of 6.5, published 29 August 2026.

Is there a fix for CVE-2026-82462?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-82462 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-82462?

Check whether you run Pac4j-Oidc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-82462: pac4j pac4j-oidc authentication bypass

CVE-2026-82462 · Severity: medium · CVSS 6.5 · Published 2026-08-29

pac4j-oidc is a Java security library that handles OpenID Connect authentication for web applications. Versions before 6.5.6 accept OIDC login callbacks with only an access token, bypassing required validation checks. An attacker can reuse access tokens from other applications to create fake authenticated sessions without proper verification, potentially gaining unauthorized access to protected applications.

Vendors: Pac4j.

Quick answers

Is CVE-2026-82462 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82462 being exploited in the wild.
How severe is CVE-2026-82462?: Medium severity, with a CVSS score of 6.5, published 29 August 2026.
Which products and versions are affected?: Pac4j-Oidc before 6.5.6.
Is there a fix for CVE-2026-82462?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-82462 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-82462?: Check whether you run Pac4j-Oidc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an OIDC authentication bypass in pac4j-oidc's OidcCredentialsExtractor component. The library accepts OIDC callbacks carrying only an access token without validating the required authorization code, ID token, issuer, audience (aud), nonce, or subject. An attacker can substitute access tokens minted for other OAuth2 clients to establish authenticated sessions in the target application. The vulnerability affects versions before 6.5.6, and patches are available in version 6.5.6 and later. No authentication is required from the attacker; exploitation occurs via crafted OIDC callback requests sent to the network-reachable application.

Affected products

pac4j pac4j-oidc before 6.5.6

Timeline

2026-08-29: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.