CVE-2026-82463
Authentication bypass in pac4j-core CheckProfileTypeAuthorizer (pre-6.5.6).
Is CVE-2026-82463 being exploited?
Not confirmed. CVE-2026-82463 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-82463?
CVE-2026-82463 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82463?
Yes. A fix has been recorded for CVE-2026-82463. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82463 affect?
CVE-2026-82463 affects pac4j-core < 6.5.6, Applications using pac4j OIDC/SAML integrations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82463?
Upgrade to pac4j-core 6.5.6+; review auth rules and access logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth bypass: attackers with weaker profiles can access resources requiring stronger profile types, enabling unauthorized access to protected resources.
Immediate action required
- affected< 6.5.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.