All reports
High

Cryptographically weak CSRF tokens in Apache MyFaces

Affected versions

Affected versions
>= 2.1.0, < 2.1.19
Fixed version
2.1.19
Affected versions
>= 2.2.0, < 2.2.14
Fixed version
2.2.14
Affected versions
< 2.0.25
Fixed version
2.0.25
Affected versions
>= 2.3.0, < 2.3.8
Fixed version
2.3.8
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2021-26296

Probability of exploitation in the next 30 days: 2.92%

FIRST EPSS · 2026-11-20

Description

In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.

Mitigation: Existing web.xml configuration parameters can be used to direct MyFaces to use SecureRandom for CSRF token generation:

org.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom org.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom org.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom

Links