dbcve.org
Parse ServerApplication · Parseplatform

CVE-2026-30965

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 8.6.21 / 9.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.8 and 8.6.21, a vulnerability in Parse Server's query handling allows an authenticated or unauthenticated attacker to exfiltrate session tokens of other users by exploiting the redirectClassNameForKey query parameter. Exfiltrated session tokens can be used to take over user accounts. The vulnerability requires the attacker to be able to create or update an object with a new relation field, which depends on the Class-Level Permissions of at least one class. This vulnerability is fixed in 9.5.2-alpha.8 and 8.6.21.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Parse Server versions prior to 9.5.2-alpha.8 and 8.6.21 contain a query handling vulnerability in the redirectClassNameForKey parameter that allows authenticated or unauthenticated attackers to exfiltrate session tokens by creating/updating objects with new relation fields, enabling account takeover.

MitigationUpgrade Parse Server to version 9.5.2-alpha.8, 8.6.21, or later to remediate the vulnerability. Review Class-Level Permissions to restrict relation field creation where possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parse ServerApplication
Affected:< 8.6.21>= 9.0.0, < 9.5.2= 9.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Parse Server version
    Check the package.json file in your Parse Server deployment directory for the 'parse-server' version entry, or query the server health endpoint if available
    Affected if The version is less than 8.6.21, or greater than or equal to 9.0.0 but less than 9.5.2-alpha.8 (including 9.5.2 exactly)
  2. Locate the redirectClassNameForKey configuration
    Search your Parse Server configuration files for the 'redirectClassNameForKey' parameter, typically found in the server config object or environment variables
    Affected if This parameter is present and configured in your Parse Server setup
  3. Verify relation field creation permissions
    Review your Class-Level Permissions (CLP) settings in the Parse Dashboard or database (_SCHEMA collection) to check if relation field creation is allowed for user classes
    Affected if Users can create or modify objects with new relation fields through the affected endpoint
  4. Check for unauthenticated access paths
    Examine your Parse Server authentication settings to determine if unauthenticated queries are permitted on user-related classes
    Affected if Unauthenticated object creation or relation field addition is allowed

You are affected if your Parse Server version falls within the vulnerable ranges and the redirectClassNameForKey parameter is in use, allowing relation field creation that could enable session token exfiltration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.6.21 / 9.5.2 or later
Fixed in 8.6.219.5.2
Interim mitigation

Upgrade Parse Server to version 9.5.2-alpha.8, 8.6.21, or later to remediate the vulnerability. Review Class-Level Permissions to restrict relation field creation where possible.

Recommended fix High confidence

Parse Server 8.6.21 (for 8.x line) or 9.5.2+ (for 9.x line)

  1. Identify the current Parse Server version running in the environment
  2. If running version 8.x (< 8.6.21): upgrade to version 8.6.21 or later
  3. If running version 9.x (>= 9.0.0, < 9.5.2, or 9.5.2): upgrade to version 9.5.2 or later (or the latest stable 9.x release)
  4. After upgrading, verify the fix by ensuring the redirectClassNameForKey query parameter no longer allows session token exfiltration
  5. Review and audit Class-Level Permissions (CLP) on all classes to ensure least-privilege access is configured
Caveat Review Parse Server migration notes for version 9.x as there may be breaking changes between major versions; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parse Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30965 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data