Privilege escalation via reversed profile type check
Published Aug 29, 2026 · Updated Aug 29, 2026
Incorrect authorization in pac4j-core before 6.5.6 allows remote authenticated users to access resources reserved for stronger profile types. CheckProfileTypeAuthorizer calls Class.isAssignableFrom with the profile class as the receiver and required type as the argument, reversing the intended subclass test. A valid login through a weaker configured client is required; successful exploitation grants the protected resource access assigned to a stronger profile type.
Summary
What happened
Incorrect authorization in pac4j-core before 6.5.6 allows remote authenticated users to access resources reserved for stronger profile types. CheckProfileTypeAuthorizer calls Class.isAssignableFrom with the profile class as the receiver and required type as the argument, reversing the intended subclass test. A valid login through a weaker configured client is required; successful exploitation grants the protected resource access assigned to a stronger profile type.
The record
- CVE
- CVE-2026-82463
- Published
- Aug 29, 2026
- Updated
- Aug 29, 2026
- Vendor
- pac4j
- Product
- pac4j
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 29, 2026CVE publishedPublication date reported by the CVE source.
- Aug 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.5.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo