Quick answers
- Is CVE-2026-82464 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82464 being exploited in the wild.
- How severe is CVE-2026-82464?
- Medium severity, with a CVSS score of 6.1, published 29 August 2026.
- Which products and versions are affected?
- Pac4j-Core before 6.5.6.
- Is there a fix for CVE-2026-82464?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82464 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82464?
- Check whether you run Pac4j-Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
pac4j-core before version 6.5.6 contains an open redirect vulnerability in the DefaultLogoutLogic.perform() method. The vulnerability occurs because the logout redirect validation logic fails to properly sanitize backslash-prefixed URLs (e.g., \\\attacker.com), which browsers normalize into network-path references (//attacker.com). An attacker can craft a logout link with a backslash-prefixed external host that passes the logoutUrlPattern validation and redirects victims to an attacker-controlled site after logout. No authentication is required; the attack vector is network-based through a crafted logout URL. The vulnerability was fixed in version 6.5.6.
Affected products
- pac4j pac4j-core before 6.5.6
Timeline
- 2026-08-29: disclosed