Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-9fjp-q3c4-6w3j

HIGHFix: parse-community/parse-server#10257

GHSA-9fjp-q3c4-6w3j is a high-severity (CVSS 7.5) CWE-674 vulnerability in parse-server. O3 Security confirms whether GHSA-9fjp-q3c4-6w3j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Parse Server has a query condition depth bypass via pre-validation transform pipeline

Also known asBIT-parse-2026-33498CVE-2026-33498
Published
Mar 20, 2026
Updated
Mar 30, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Mar 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
📦parse-server📦parse-server

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

Description

Impact

An attacker can send an unauthenticated HTTP request with a deeply nested query containing logical operators to permanently hang the Parse Server process. The server becomes completely unresponsive and must be manually restarted. This is a bypass of the fix for CVE-2026-32944.

Patches

The query condition nesting depth is now validated before the query enters the transformation pipeline, preventing deeply nested structures from being recursively processed before the existing depth guard can fire.

Workarounds

None.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmparse-server9.0.0&&< 9.6.0-alpha.449.6.0-alpha.44
📦npmparse-serverall versions8.6.55

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update parse-server to 9.6.0-alpha.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9fjp-q3c4-6w3j is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9fjp-q3c4-6w3j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9fjp-q3c4-6w3j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An attacker can send an unauthenticated HTTP request with a deeply nested query containing logical operators to permanently hang the Parse Server process. The server becomes completely unresponsive and must be manually restarted. This is a bypass of the fix for CVE-2026-32944. ### Patches The query condition nesting depth is now validated before the query enters the transformation pipeline, preventing deeply nested structures from being recursively processed before the existing depth guard can fire. ### Workarounds None.
O3 Security · Impact-Aware SCA

Is GHSA-9fjp-q3c4-6w3j in your dependencies?

O3 detects GHSA-9fjp-q3c4-6w3j across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-9fjp-q3c4-6w3j: parse-server (High 7.5) | O3 Security