pac4j-core before 6.5.6 contains an authentication bypass vulnerability in CheckProfileTypeAuthorizer that reverses the profile type validation logic. Attackers can authenticate through a weaker client and access resources requiring a stronger profile type by satisfying generic profile checks.
CVE-2026-82463
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-29. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (5)
Auto-updated Aug 29, 2026pac4j-core before 6.5.6 Authorization Bypass via Reversed Profile Type Check | Advisories | VulnCheck
https://www.vulncheck.com/advisories/pac4j-core-before-6.5.6-authorization-bypass-via-reversed-profile-type-checkGitHub - pac4j/pac4j: Security engine for Java (authentication, authorization, multi frameworks): OpenID Connect, SAML2, CAS, OAuth, LDAP, JWT... · GitHub
https://github.com/pac4j/pac4jpac4j/pac4j-core/src/main/java/org/pac4j/core/authorization/authorizer/CheckProfileTypeAuthorizer.java at pac4j-parent-6.5.5 · pac4j/pac4j · GitHub
https://github.com/pac4j/pac4j/blob/pac4j-parent-6.5.5/pac4j-core/src/main/java/org/pac4j/core/authorization/authorizer/CheckProfileTypeAuthorizer.javaSecurity advisory for pac4j-core, pac4j-oidc and pac4j-saml | pac4j
https://www.pac4j.org/blog/security-advisory-pac4j-core-oidc-saml.htmlcommit 2270c3ff70e9 (pac4j/pac4j)
Fix landed in pac4j/pac4j commit 2270c3ff70e9 — awaiting tagged release
https://github.com/pac4j/pac4j/commit/2270c3ff70e93cc43831e75702acd5135531237eVendor Advisories for CVE-2026-82463(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 5× in last 7d / 5× 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.
- 2026-08-30 05:23 UTCEG score recompute
- 2026-08-30 05:23 UTCGHSA enrichment
- 2026-08-29 17:28 UTCEG score recompute
- 2026-08-29 16:41 UTCEG score recompute
- 2026-08-29 16:37 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-82463?
When was CVE-2026-82463 disclosed?
What is the CVSS score of CVE-2026-82463?
How do I remediate CVE-2026-82463?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82463
Is Your Infrastructure Affected by CVE-2026-82463?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.