CVE-2026-82462: pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution

Published Aug 29, 2026
·
Updated

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.

Affected Software

1 affected component
pac4j-oidc<6.5.6

Event History

Aug 29, 2026
CVE Published
via MITRE·04:35 PM
Data Sourced
via MITRE·04:35 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using pac4j-oidc versions earlier than 6.5.6 are affected.

2

What does an attacker need to exploit this issue?

An attacker needs an OIDC callback that carries only an access token, including an access token minted for a different client. No authorization code or ID token validation is required by the affected behavior.

3

What validation is bypassed during exploitation?

The affected callback handling can create an authenticated session without proper verification of the token issuer, audience, nonce, or subject.

4

What is the available remediation?

Update pac4j-oidc to version 6.5.6 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203