dbcve.org
Parse ServerApplication · Parseplatform

CVE-2026-30863

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 8.6.10 / 9.5.0 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 versions 8.6.10 and 9.5.0-alpha.11, the Google, Apple, and Facebook authentication adapters use JWT verification to validate identity tokens. When the adapter's audience configuration option is not set (clientId for Google/Apple, appIds for Facebook), JWT verification silently skips audience claim validation. This allows an attacker to use a validly signed JWT issued for a different application to authenticate as any user on the target Parse Server. This issue has been patched in versions 8.6.10 and 9.5.0-alpha.11.

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's Google, Apple, and Facebook authentication adapters skip JWT audience claim validation when the audience configuration (clientId or appIds) is not set. This allows attackers to reuse validly signed JWTs from other applications to authenticate as any user on the affected Parse Server.

MitigationUpgrade to Parse Server version 8.6.10 or 9.5.0-alpha.11, or ensure the clientId/appIds configuration options are properly set for all OAuth adapters.

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.10>= 9.0.0, < 9.5.0= 9.5.0

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
High

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

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. Check Parse Server version
    Run 'parse-server --version' or check the version in your package.json or running process
    Affected if The version is < 8.6.10, or >= 9.0.0 and < 9.5.0, or exactly 9.5.0
  2. Identify configured OAuth adapters
    Review your Parse Server configuration file or environment variables for authadapters, google, apple, or facebook provider settings
    Affected if Any of Google, Apple, or Facebook OAuth adapters are configured for user authentication
  3. Verify clientId/appIds configuration for OAuth providers
    Inspect the configuration for each OAuth adapter (google, apple, facebook) and check if clientId or appIds fields are populated with valid values
    Affected if One or more OAuth adapters have clientId or appIds configuration missing or left undefined/empty

You are affected if you run a vulnerable Parse Server version AND have Google, Apple, or Facebook OAuth adapters enabled WITHOUT proper clientId/appIds configuration for at least one provider.

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.10 / 9.5.0 or later
Fixed in 8.6.109.5.0
Interim mitigation

Upgrade to Parse Server version 8.6.10 or 9.5.0-alpha.11, or ensure the clientId/appIds configuration options are properly set for all OAuth adapters.

Recommended fix High confidence

Parse Server 8.6.10 (for 8.x line) or Parse Server 9.5.0 (for 9.x line)

  1. 1. Identify your current Parse Server version by checking your package.json or running `parse-server --version`
  2. 2. For Parse Server 8.x: Upgrade to version 8.6.10 or later by running `npm install parse-server@^8.6.10`
  3. 3. For Parse Server 9.x: Upgrade to version 9.5.0 or later (the fix is in 9.5.0-alpha.11 and stable 9.5.0) by running `npm install parse-server@^9.5.0`
  4. 4. After upgrading, verify that the Google, Apple, and Facebook authentication adapters have the audience configuration options properly set (clientId for Google/Apple, appIds for Facebook) to ensure JWT audience validation occurs
  5. 5. Test authentication flows with Google, Apple, and Facebook to confirm the fix works correctly
  6. 6. Review your deployment for any other Parse Server instances that may need updating
Caveat Review the Parse Server changelog between your current version and the target version for any breaking changes, especially for authentication-related modifications

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

Fix this in Parse Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30863 — 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-30863 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