How severe is GHSA-w73w-g5xw-rwhf?

No CVSS score has been assigned to GHSA-w73w-g5xw-rwhf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w73w-g5xw-rwhf?

GHSA-w73w-g5xw-rwhf affects the following packages: parse-server (npm), parse-server (npm). Ecosystems affected: npm.

How do I fix GHSA-w73w-g5xw-rwhf?

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

How do I detect GHSA-w73w-g5xw-rwhf 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-w73w-g5xw-rwhf 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-w73w-g5xw-rwhf actively exploited in the wild?

No public exploit code has been indexed for GHSA-w73w-g5xw-rwhf 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-w73w-g5xw-rwhf?

GHSA-w73w-g5xw-rwhf has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-w73w-g5xw-rwhf?

GHSA-w73w-g5xw-rwhf is classified as CWE-367 (CWE-367). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w73w-g5xw-rwhf published, and has it been updated?

GHSA-w73w-g5xw-rwhf was published on March 29, 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 an MFA single-use token bypass via concurrent authData login requestsGHSA-w73w-g5xw-rwhf

Fix: parse-community/parse-server#10326

GHSA-w73w-g5xw-rwhf is a CWE-367 vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Also known asBIT-parse-2026-34224CVE-2026-34224

Published

Mar 29, 2026

Updated

Apr 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-w73w-g5xw-rwhf.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% 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

51Kdownloads / week

Description

Impact

An attacker who possesses a valid authentication provider token and a single MFA recovery code or SMS one-time password can create multiple authenticated sessions by sending concurrent login requests via the authData login endpoint. This defeats the single-use guarantee of MFA recovery codes and SMS one-time passwords, allowing session persistence even after the legitimate user revokes detected sessions.

Patches

The fix adds optimistic locking to the authData login path, ensuring that concurrent database updates for the same user fail when the original MFA token array has already been modified by another request.

Workarounds

There is no known workaround.

Affected Packages

2 total 2 fixed

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

Affected Products

1 product · 9 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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w73w-g5xw-rwhf 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 attacker who possesses a valid authentication provider token and a single MFA recovery code or SMS one-time password can create multiple authenticated sessions by sending concurrent login requests via the authData login endpoint. This defeats the single-use guarantee of MFA recovery codes and SMS one-time passwords, allowing session persistence even after the legitimate user revokes detected sessions. ### Patches The fix adds optimistic locking to the authData login path, ensuring that concurrent database updates for the same user fail when the original MFA token array has alr

O3 Security · Impact-Aware SCA

Is GHSA-w73w-g5xw-rwhf in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works