How severe is GHSA-4q3h-vp4r-prv2?

No CVSS score has been assigned to GHSA-4q3h-vp4r-prv2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4q3h-vp4r-prv2?

GHSA-4q3h-vp4r-prv2 affects the following packages: parse-server (npm), parse-server (npm). Ecosystems affected: npm.

How do I fix GHSA-4q3h-vp4r-prv2?

Update parse-server to 9.3.1-alpha.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4q3h-vp4r-prv2 is resolved across your whole dependency graph.

How do I detect GHSA-4q3h-vp4r-prv2 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-4q3h-vp4r-prv2 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-4q3h-vp4r-prv2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4q3h-vp4r-prv2 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-4q3h-vp4r-prv2?

GHSA-4q3h-vp4r-prv2 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th 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-4q3h-vp4r-prv2?

GHSA-4q3h-vp4r-prv2 is classified as Broken Cryptographic Algorithm (CWE-327), CWE-345 (CWE-345). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4q3h-vp4r-prv2 published, and has it been updated?

GHSA-4q3h-vp4r-prv2 was published on February 25, 2026 and was last updated on March 2, 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: Account takeover via JWT algorithm confusion in Google auth adapterGHSA-4q3h-vp4r-prv2

Fix: parse-community/parse-server@9b94083

GHSA-4q3h-vp4r-prv2 is a Broken Cryptographic Algorithm vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Also known asBIT-parse-2026-27804CVE-2026-27804

Published

Feb 25, 2026

Updated

Mar 2, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 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.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-4q3h-vp4r-prv2.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk+0.03%

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

70Kdownloads / week

Description

Impact

An unauthenticated attacker can forge a Google authentication token with alg: "none" to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected.

Patches

The fix hardcodes the expected RS256 algorithm instead of trusting the JWT header, and replaces the Google adapter's custom key fetcher with jwks-rsa which rejects unknown key IDs.

Workarounds

Disable Google authentication until you can upgrade.

References

GitHub advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4q3h-vp4r-prv2
Fixed in Parse Server 9.3.1-alpha.4: https://github.com/parse-community/parse-server/releases/tag/9.3.1-alpha.4
Fixed in Parse Server 8.6.3: https://github.com/parse-community/parse-server/releases/tag/8.6.3

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`parse-server`	≥ 9.0.0&&< 9.3.1-alpha.4	9.3.1-alpha.4`npm install parse-server@9.3.1-alpha.4`
📦npm	`parse-server`	all versions	8.6.3`npm install parse-server@8.6.3`

Affected Products

1 product · 5 configurations

Application

parse-serverparseplatform

≥ 9.0.0 && < 9.3.1

1 version

9.3.1

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.3.1-alpha.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4q3h-vp4r-prv2 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 unauthenticated attacker can forge a Google authentication token with `alg: "none"` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. ### Patches The fix hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter's custom key fetcher with `jwks-rsa` which rejects unknown key IDs. ### Workarounds Disable Google authentication until you can upgrade. ### References - GitHub advisory: https://github.com/parse-community/parse-serv

O3 Security · Impact-Aware SCA

Is GHSA-4q3h-vp4r-prv2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works