CVE-2026-82462

pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution

Published Aug 29, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification.

Analysis

AI-generated

Technical impact

pac4j-oidc before version 6.5.6 is vulnerable to an authentication bypass that occurs when the library accepts OIDC callbacks containing only an access token. The access token supplied by an attacker can be one that was issued to a different client, and the library does not perform issuer, audience, nonce, or subject validation. As a result, an attacker can substitute a token, cause the application to establish a session, and gain unauthorized access as the substituted subject.

Affected Systems

Any Java application that incorporates the pac4j library and uses pac4j-oidc for OpenID Connect authentication, specifically when running a version of pac4j-oidc earlier than 6.5.6, is at risk. This includes applications that rely on pac4j to extract credentials and create user sessions from OIDC callbacks.

Risk and Exploitability

The CVSS score of 6.9 indicates a moderate severity, and the attack can be executed remotely by sending a crafted OIDC callback request to the application’s callback endpoint that carries only an access token without accompanying authorization code or ID token. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalog, but the ability to impersonate users and establish unauthorized sessions makes it a serious security concern.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade pac4j-oidc to version 6.5.6 or later, which implements proper validation of issuer, audience, nonce, and subject.
  • If an immediate upgrade is not possible, add server‑side checks that reject OIDC callbacks which contain only an access token and require validation of the token’s issuer, audience, and nonce before establishing a session.
  • Configure or enforce the application to verify that the client ID in the callback matches the one configured for the application, and drop any callback request that does not satisfy this validation.

Generated by OpenCVE AI on August 29, 2026 at 17:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification.
Title pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution
First Time appeared Pac4j
Pac4j pac4j
Weaknesses CWE-345
CPEs cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*
Vendors & Products Pac4j
Pac4j pac4j
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 31, 2026, 6:19 PM
Reserved
Aug 29, 2026, 2:11 PM
Status
Awaiting Analysis
Published
Aug 29, 2026, 5:17 PM
Modified
Sep 10, 2026, 7:54 PM