CSRF in Pac4j
CVE-2026-40458
PAC4J is vulnerable to Cross-Site Request Forgery (CSRF). A malicious attacker can craft a specially designed website which, when visited by a user, will automatically submit a forged cross-site request with a token whose hash collides with the victim's legitimate CSRF token. Importantly, the attacker does not need to know the victim’s CSRF token or its hash prior to the attack. Collisions in the deterministic String.hashCode() function can be computed directly, reducing the effective token's security space to 32 bits. This bypasses CSRF protection, allowing profile updates, password changes, account linking, and any other state-changing operations to be performed without the victim's consent.
This issue was fixed in PAC4J versions 5.7.10 and 6.4.1
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS 0.002, 6.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Pac4j — versions 5.0, 6.0
Weakness classification (CWE)
References
- cert.pl/en/posts/2026/04/CVE-2026-40458/ (Third Party Advisory, third-party-advisory)
- www.pac4j.org/blog/security-advisory-pac4j-core-and-ldap.html (vendor-advisory, Vendor Advisory)