How severe is GHSA-gq67-pp9w-43gp?

No CVSS score has been assigned to GHSA-gq67-pp9w-43gp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gq67-pp9w-43gp?

GHSA-gq67-pp9w-43gp affects the following packages: org.apache.myfaces.core:myfaces-core-module (Maven), org.apache.myfaces.core:myfaces-core-module (Maven), org.apache.myfaces.core:myfaces-core-module (Maven), org.apache.myfaces.core:myfaces-core-module (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gq67-pp9w-43gp?

Update org.apache.myfaces.core:myfaces-core-module to 2.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq67-pp9w-43gp is resolved across your whole dependency graph.

How do I detect GHSA-gq67-pp9w-43gp in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.core:myfaces-core-module, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gq67-pp9w-43gp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-gq67-pp9w-43gp actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-gq67-pp9w-43gp, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-gq67-pp9w-43gp?

GHSA-gq67-pp9w-43gp has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gq67-pp9w-43gp?

GHSA-gq67-pp9w-43gp is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gq67-pp9w-43gp published, and has it been updated?

GHSA-gq67-pp9w-43gp was published on June 16, 2021 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Cryptographically weak CSRF tokens in Apache MyFacesGHSA-gq67-pp9w-43gp

Fix: apache/myfaces@cc6e1cc

GHSA-gq67-pp9w-43gp is a Cross-Site Request Forgery (CSRF) vulnerability in org.apache.myfaces.core:myfaces-core-module. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.apache.myfaces.core:myfaces-core-module — see the affected versions and patch details below.

Also known asCVE-2021-26296

Published

Jun 16, 2021

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

☕org.apache.myfaces.core:myfaces-core-module☕org.apache.myfaces.core:myfaces-core-module☕org.apache.myfaces.core:myfaces-core-module☕org.apache.myfaces.core:myfaces-core-module

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	all versions	2.0.25`org.apache.myfaces.core:myfaces-core-module:2.0.25`
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	≥ 2.1.0&&< 2.1.19	2.1.19`org.apache.myfaces.core:myfaces-core-module:2.1.19`
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	≥ 2.2.0&&< 2.2.14	2.2.14`org.apache.myfaces.core:myfaces-core-module:2.2.14`
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	≥ 2.3.0&&< 2.3.8	2.3.8`org.apache.myfaces.core:myfaces-core-module:2.3.8`

Affected Products

2 products · 8 configurations

Application

myfacesapache

≥ 2.3.0 && ≤ 2.3.7

2 versions

2.33.0.0

Application

oncommand insightnetapp

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.…

packetstormsecurity.comNVDJun 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.core:myfaces-core-module, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.myfaces.core:myfaces-core-module to 2.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq67-pp9w-43gp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-gq67-pp9w-43gp in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works