Cryptographically weak CSRF tokens in Apache MyFaces

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2021-26296: 2.89% estimated exploitation activity in the next 30 days; percentile 86.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.RANDOMKEYINVIEWSTATESESSIONTOKEN=secureRandom org.apache.myfaces.RANDOMKEYINCSRFSESSIONTOKEN=secureRandom org.apache.myfaces.RANDOMKEYINWEBSOCKETSESSIONTOKEN=secureRandom

Published by the source

16 Jun 2021, 17:31 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gq67-pp9w-43gp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-26296

Advisory: Cryptographically weak CSRF tokens in Apache MyFaces
IDs: CVE-2021-26296, GHSA-gq67-pp9w-43gp
Record: https://patchnext.com/advisories/cve-2021-26296 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.myfaces.core:myfaces-core-module 2.3.8, 2.2.14, 2.1.19, 2.0.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.myfaces.core:myfaces-core-module: affected < 2.0.25; >= 2.1.0, < 2.1.19; >= 2.2.0, < 2.2.14; >= 2.3.0, < 2.3.8; fixed in 2.0.25, 2.1.19, 2.2.14, 2.3.8

## Suggested inspection (read-only)
- Maven org.apache.myfaces.core:myfaces-core-module: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.myfaces.core:myfaces-core-module.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gq67-pp9w-43gp (GitHub-reviewed advisory GHSA-gq67-pp9w-43gp lists affected ranges: Maven org.apache.myfaces.core:myfaces-core-module >=0 =2.1.0 =2.2.0 =2.3.0 <2.3.8)

Commands are suggestions: review each one before running it.