Advisory record · GHSA-xw5c-jc7x-gf75

PAC4J has a Cross-Site Request Forgery (CSRF) Vulnerability

CVSS 7.0 HighEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 17 Apr 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.pac4j:pac4j-coreMaven<5.7.10 || >=6.0.0-RC1, <6.4.15.7.10, 6.4.1
Identifiers
GHSA-xw5c-jc7x-gf75 · CVE-2026-40458
Weakness (CWE)
CWE-352
Published
17 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

PAC4J (pac4j-core) versions before 5.7.10, and versions from 6.0.0-RC1 before 6.4.1, are vulnerable to cross-site request forgery. An attacker can host a crafted website that, when a logged-in user visits it, submits a forged request with a token that collides with the victim's CSRF token, since the token's hash can be computed without knowing the victim's token. This allows state-changing actions such as profile updates, password changes, and account linking without the user's consent. Upgrade pac4j-core to 5.7.10 or 6.4.1.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.0 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N CNA (CERT-PL)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.