CVE-2026-82462

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-29. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 29, 2026

Last Modified

September 10, 2026

Advisory Details (5)

Auto-updated Aug 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pac4j-oidc-before-6.5.6-authentication-bypass-via-access-token-substitution
generic

GitHub - pac4j/pac4j: Security engine for Java (authentication, authorization, multi frameworks): OpenID Connect, SAML2, CAS, OAuth, LDAP, JWT... · GitHub

https://github.com/pac4j/pac4j
generic

pac4j/pac4j-oidc/src/main/java/org/pac4j/oidc/credentials/extractor/OidcCredentialsExtractor.java at pac4j-parent-6.5.5 · pac4j/pac4j · GitHub

https://github.com/pac4j/pac4j/blob/pac4j-parent-6.5.5/pac4j-oidc/src/main/java/org/pac4j/oidc/credentials/extractor/OidcCredentialsExtractor.java
generic

Security advisory for pac4j-core, pac4j-oidc and pac4j-saml | pac4j

https://www.pac4j.org/blog/security-advisory-pac4j-core-oidc-saml.html
github_commit

commit 2270c3ff70e9 (pac4j/pac4j)

Fix landed in pac4j/pac4j commit 2270c3ff70e9 — awaiting tagged release

https://github.com/pac4j/pac4j/commit/2270c3ff70e93cc43831e75702acd5135531237e

Vendor Advisories for CVE-2026-82462(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 20:49 UTCEG score recompute
  2. 2026-09-19 20:49 UTCGHSA enrichment
  3. 2026-09-18 21:27 UTCEG score recompute
  4. 2026-09-18 21:27 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 20:49 UTCEG score recompute
  7. 2026-09-17 20:49 UTCGHSA enrichment
  8. 2026-09-16 18:51 UTCEG score recompute
  9. 2026-09-16 18:50 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 18:27 UTCEG score recompute
  13. 2026-09-15 18:27 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 18:45 UTCGHSA enrichment
  17. 2026-09-13 18:07 UTCEG score recompute
  18. 2026-09-13 18:07 UTCGHSA enrichment
  19. 2026-09-12 18:45 UTCEG score recompute
  20. 2026-09-12 18:45 UTCGHSA enrichment
  21. 2026-09-11 19:23 UTCEG score recompute
  22. 2026-09-11 19:23 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 20:01 UTCEG score recompute
Show 38 more
  1. 2026-09-10 20:01 UTCGHSA enrichment
  2. 2026-09-09 23:51 UTCGHSA enrichment
  3. 2026-09-09 00:24 UTCEG score recompute
  4. 2026-09-09 00:24 UTCGHSA enrichment
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 17:08 UTCEG score recompute
  7. 2026-09-07 17:08 UTCGHSA enrichment
  8. 2026-09-06 17:47 UTCEG score recompute
  9. 2026-09-06 17:47 UTCGHSA enrichment
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-05 18:25 UTCEG score recompute
  12. 2026-09-05 18:25 UTCGHSA enrichment
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-04 19:03 UTCEG score recompute
  15. 2026-09-04 19:03 UTCGHSA enrichment
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-03 19:40 UTCGHSA enrichment
  18. 2026-09-02 20:16 UTCEG score recompute
  19. 2026-09-02 20:16 UTCGHSA enrichment
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 18:52 UTCEG score recompute
  22. 2026-09-01 18:52 UTCGHSA enrichment
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-31 19:29 UTCEG score recompute
  27. 2026-08-31 19:29 UTCGHSA enrichment
  28. 2026-08-31 18:33 UTCEG score recompute
  29. 2026-08-31 18:33 UTCGHSA enrichment
  30. 2026-08-31 16:43 UTCEG score recompute
  31. 2026-08-31 16:43 UTCGHSA enrichment
  32. 2026-08-30 19:18 UTCEPSS rescore
  33. 2026-08-30 19:17 UTCEPSS rescore
  34. 2026-08-30 16:50 UTCEG score recompute
  35. 2026-08-30 16:50 UTCGHSA enrichment
  36. 2026-08-29 17:28 UTCEG score recompute
  37. 2026-08-29 16:42 UTCEG score recompute
  38. 2026-08-29 16:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82462?
CVE-2026-82462 is a medium vulnerability published on August 29, 2026. 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.
When was CVE-2026-82462 disclosed?
CVE-2026-82462 was first published in the National Vulnerability Database on August 29, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82462 actively exploited?
CVE-2026-82462 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-82462?
CVE-2026-82462 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-82462?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82462, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82462

Explore →

Is Your Infrastructure Affected by CVE-2026-82462?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs