How severe is GHSA-f6j3-w9v3-cq22?

No CVSS score has been assigned to GHSA-f6j3-w9v3-cq22 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f6j3-w9v3-cq22?

GHSA-f6j3-w9v3-cq22 affects the following packages: parse-server (npm), parse-server (npm). Ecosystems affected: npm.

How do I fix GHSA-f6j3-w9v3-cq22?

Update parse-server to 9.7.0-alpha.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6j3-w9v3-cq22 is resolved across your whole dependency graph.

How do I detect GHSA-f6j3-w9v3-cq22 in my npm dependencies?

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

How do I mitigate GHSA-f6j3-w9v3-cq22 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-f6j3-w9v3-cq22 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f6j3-w9v3-cq22 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-f6j3-w9v3-cq22?

GHSA-f6j3-w9v3-cq22 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th 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-f6j3-w9v3-cq22?

GHSA-f6j3-w9v3-cq22 is classified as CWE-697 (CWE-697). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f6j3-w9v3-cq22 published, and has it been updated?

GHSA-f6j3-w9v3-cq22 was published on April 1, 2026 and was last updated on April 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Parse Server has a session field immutability bypass via falsy-value guardGHSA-f6j3-w9v3-cq22

Fix: parse-community/parse-server#10347

GHSA-f6j3-w9v3-cq22 is a CWE-697 vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Also known asBIT-parse-2026-34574CVE-2026-34574

Published

Apr 1, 2026

Updated

Apr 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f6j3-w9v3-cq22.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

62other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

parse-servernpm

54Kdownloads / week

Description

Impact

An authenticated user can bypass the immutability guard on session fields (expiresAt, createdWith) by sending a null value in a PUT request to the session update endpoint. This allows nullifying the session expiry, making the session valid indefinitely and bypassing configured session length policies.

Patches

The truthiness-based guard checks were replaced with key-presence checks that reject any value for protected session fields, including null.

Workarounds

There is no known workaround. A beforeSave trigger on _Session could be used to reject null values for expiresAt and createdWith.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`parse-server`	≥ 9.0.0&&< 9.7.0-alpha.14	9.7.0-alpha.14`npm install parse-server@9.7.0-alpha.14`
📦npm	`parse-server`	all versions	8.6.69`npm install parse-server@8.6.69`

Affected Products

1 product · 15 configurations

Application

parse-serverparseplatform

≥ 9.0.0 && < 9.7.0

1 version

9.7.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-server to 9.7.0-alpha.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6j3-w9v3-cq22 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

### Impact An authenticated user can bypass the immutability guard on session fields (`expiresAt`, `createdWith`) by sending a null value in a PUT request to the session update endpoint. This allows nullifying the session expiry, making the session valid indefinitely and bypassing configured session length policies. ### Patches The truthiness-based guard checks were replaced with key-presence checks that reject any value for protected session fields, including null. ### Workarounds There is no known workaround. A `beforeSave` trigger on `_Session` could be used to reject null values for `

O3 Security · Impact-Aware SCA

Is GHSA-f6j3-w9v3-cq22 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works