/

CVE-2026-82463

Severity:

HIGH RISK

(8.1)

Authorization Bypass (CWE-863) in pac4j-core Java Library

CVE-2026-82463

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Unauthorized Access

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A flaw in pac4j-core causes CheckProfileTypeAuthorizer to apply profile type validation in reverse, allowing weaker authenticated profiles to satisfy checks intended for stronger profile types. Under affected authorization configurations, an attacker may access protected resources without meeting the required authentication assurance level.

Affected context

The vulnerability occurs in applications using pac4j-core's CheckProfileTypeAuthorizer to enforce profile type or authentication-level requirements. Risk depends on an authorization policy that distinguishes between weaker and stronger client profiles and on the application relying on the affected validation behavior to protect resources.

Exploit preconditions

  • Attack surface: Application authorization checks that use CheckProfileTypeAuthorizer
  • Required access: Ability to authenticate through a client or profile type accepted by the application
  • Trigger point: Authorization of a resource requiring a stronger profile type
  • Why exploitation is possible: Reversed validation logic can treat a generic or weaker profile as satisfying a stronger profile requirement

Why this happens

The underlying bug is an authorization logic error in profile type validation. Instead of correctly confirming that the authenticated profile meets the required type or assurance level, the check reverses the relationship between the presented and required profiles. This maps to CWE-863: Incorrect Authorization, where access-control decisions incorrectly grant permissions to an authenticated subject.

Potential impact

  • Attackers may access resources intended for stronger-authenticated users
  • Applications could expose sensitive data or privileged operations
  • Administrative or high-assurance workflows may be reachable through weaker clients
  • Organizations may experience unauthorized changes, data disclosure, or compliance impact

General mitigation guidance

Mitigation typically focuses on making authorization decisions explicit, monotonic, and independent of ambiguous profile comparisons.

Common defensive patterns include:

  • Use corrected authorization logic that verifies the presented profile meets or exceeds the required profile type
  • Prefer secure-by-default policies that deny access when profile classification is missing, ambiguous, or unexpected
  • Reduce trust in client-supplied profile attributes by deriving assurance from server-controlled authentication state
  • Apply least privilege and separate high-assurance resources from general authentication paths
  • Add tests covering weaker, equal, stronger, unknown, and absent profile types
  • Review authorization behavior at integration boundaries rather than relying solely on generic profile checks

How teams detect issues like this

Organizations can detect this class of issue through:

  • Static analysis and code review for inverted comparisons, reversed subtype checks, and default-allow authorization branches
  • Policy tests that verify weaker authentication profiles cannot access stronger-profile resources
  • Integration tests covering every supported client and profile combination
  • Runtime monitoring for lower-assurance clients accessing privileged endpoints
  • Automated dependency and security review tools that flag vulnerable authorization components
  • Enforcement of centralized authorization policies with explicit deny behavior for unrecognized profile types

Sources

SourceLink
github.comgithub.com/pac4j/pac4j
github.comgithub.com/pac4j/pac4j/blob/pac4j-parent-6.5.5/pac4j-core/src/main/java/org/pac4j/core/authorization/authorizer/CheckProfileTypeAuthorizer.java
github.comgithub.com/pac4j/pac4j/commit/2270c3ff70e93cc43831e75702acd5135531237e
pac4j.orgpac4j.org/blog/security-advisory-pac4j-core-oidc-saml.html
vulncheck.comvulncheck.com/advisories/pac4j-core-before-6.5.6-authorization-bypass-via-reversed-profile-type-check

Frequently asked

questions

It may be exploitable through an application's exposed authentication and authorization flows when those flows use the affected profile validation behavior.

An attacker generally needs to authenticate through an available weaker client or profile type and request a resource protected by a stronger profile requirement.

Use authorization logic that explicitly verifies the authenticated profile meets the required assurance level and denies access when profile information is incomplete or unexpected.

Maintain centralized, deny-by-default authorization policies and test all profile combinations, especially transitions between generic, weaker, and stronger authentication methods.

Find out what's already
exploitable in your codebase.