Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-32269: 0.29% estimated exploitation activity in the next 30 days; percentile 21.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patches The fix corrects the parameter alignment in the OAuth2 adapter's app ID validation method to match the expected interface, ensuring the correct access token is sent to the introspection endpoint. Workarounds There is no known workaround. References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-69xg-f649-w5g2 - Fix in Parse Server 9:…

Published by the source

13 Mar 2026, 20:02 UTC

Last modified by the source

16 Mar 2026, 10:40 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-69xg-f649-w5g2

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-69xg-f649-w5g2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32269

Advisory: Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint
IDs: CVE-2026-32269, GHSA-69xg-f649-w5g2
Record: https://patchnext.com/advisories/cve-2026-32269 (revision 3, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse-server 9.6.0-alpha.13, 8.6.39. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse-server: affected >= 9.0.0, < 9.6.0-alpha.13; >= 8.0.2, < 8.6.39; fixed in 9.6.0-alpha.13, 8.6.39

## Suggested inspection (read-only)
- `npm ls parse-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-69xg-f649-w5g2 (OSV record GHSA-69xg-f649-w5g2 lists affected ranges: npm parse-server >=9.0.0 =8.0.2 <8.6.39 (fixed))
- Verified: https://github.com/advisories/GHSA-69xg-f649-w5g2 (GitHub-reviewed advisory GHSA-69xg-f649-w5g2 lists affected ranges: npm parse-server >=9.0.0 =8.0.2 <8.6.39)

Commands are suggestions: review each one before running it.