dbcve.org
Parse ServerApplication · Parseplatform

CVE-2026-32269

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 8.6.39 / 9.6.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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.6.0-alpha.13 and 8.6.39, the OAuth2 authentication adapter does not correctly validate app IDs when appidField and appIds are configured. During app ID validation, a malformed value is sent to the token introspection endpoint instead of the user's actual access token. Depending on the introspection endpoint's behavior, this could either cause all OAuth2 logins to fail, or allow authentication from disallowed app contexts if the endpoint returns valid-looking data for the malformed request. Deployments using the OAuth2 adapter with appidField and appIds configured are affected. This vulnerability is fixed in 9.6.0-alpha.13 and 8.6.39.

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

The OAuth2 authentication adapter in Parse Server incorrectly validates app IDs when appidField and appIds are configured. During validation, a malformed value is sent to the token introspection endpoint instead of the user's actual access token, which can either cause all OAuth2 logins to fail or potentially allow authentication from disallowed app contexts if the endpoint returns valid-looking data for the malformed request.

MitigationUpgrade Parse Server to version 9.6.0-alpha.13 or 8.6.39. Until patched, avoid using OAuth2 adapter with appidField and appIds configuration.

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.0.2, < 8.6.39>= 9.0.0, < 9.6.0= 9.6.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check Parse Server version
    Run `npm list parse-server` or check your package.json to identify the installed version of parse-server
    Affected if Installed version is >= 8.0.2 and < 8.6.39; OR >= 9.0.0 and < 9.6.0; OR exactly 9.6.0
  2. Identify OAuth2 authentication configuration
    Examine your Parse Server configuration files and authentication setup to determine if OAuth2 adapter is in use. Look for OAuth2-related configuration in your authentication providers setup
    Affected if OAuth2 authentication adapter is configured and in use
  3. Verify appidField configuration
    Inspect your OAuth2 adapter configuration for the presence of an appidField parameter. This is typically set in the OAuth2 authentication options or configuration file
    Affected if appidField is explicitly configured in the OAuth2 adapter settings
  4. Check appIds configuration
    Inspect your OAuth2 adapter configuration for the presence of an appIds parameter. This is typically an array or list of allowed app IDs defined in the OAuth2 authentication options
    Affected if appIds is configured with one or more app IDs in the OAuth2 adapter settings

You are affected if your Parse Server version falls within the affected ranges AND you use OAuth2 authentication with both appidField and appIds configured together.

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.39 / 9.6.0 or later
Fixed in 8.6.399.6.0
Interim mitigation

Upgrade Parse Server to version 9.6.0-alpha.13 or 8.6.39. Until patched, avoid using OAuth2 adapter with appidField and appIds configuration.

Recommended fix High confidence

parse-server 8.6.39 (8.x branch) or 9.6.1+/9.6.0-alpha.13 (9.x branch)

  1. 1. Identify current Parse Server version by checking package.json or running `parse-server --version`
  2. 2. If running 8.x branch (>= 8.0.2): upgrade to parse-server version 8.6.39 or later (e.g., npm install [email protected])
  3. 3. If running 9.x branch (>= 9.0.0, including 9.6.0): upgrade to parse-server version 9.6.1 or later if available, or to 9.6.0-alpha.13 as a temporary measure until a stable 9.6.x fix is released
  4. 4. After upgrading, verify OAuth2 authentication still works correctly with your configured appidField and appIds
  5. 5. Test that the token introspection endpoint receives the correct access token value (not a malformed value)
Caveat Review release notes for version 8.6.39 and 9.6.x for any breaking changes before upgrading; OAuth2 configurations using appidField and appIds should be retested

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

Fix this in Parse Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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