Cross-site Request Forgery (CSRF) Affecting druid package, versions <36.0.0-r15


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.02% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Cross-site Request Forgery (CSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-WOLFILATEST-DRUID-16379992
  • published4 May 2026
  • disclosed17 Apr 2026

Introduced: 17 Apr 2026

NewCVE-2026-40458  (opens in a new tab)
CWE-352  (opens in a new tab)

How to fix?

Upgrade Wolfi druid to version 36.0.0-r15 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream druid package and not the druid package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

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

CVSS Base Scores

version 3.1