cve.bz

CVE-2026-32269 parseplatform parse-server

6.3 mediumEPSS 0.3%Fix available

Medium (6.3) in parseplatform parse-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.39, 9.6.0-alpha.13.

On this page
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.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-683 Function Call With Incorrect Order of Arguments
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32269 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32269?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32269?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32269 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverfrom 8.0.2 before 8.6.39
parseplatform:parse-serverfrom 9.0.0 before 9.6.0
parseplatform:parse-server9.6.0:alpha1
parseplatform:parse-server9.6.0:alpha10
parseplatform:parse-server9.6.0:alpha11
parseplatform:parse-server9.6.0:alpha12
parseplatform:parse-server9.6.0:alpha2
parseplatform:parse-server9.6.0:alpha3
parseplatform:parse-server9.6.0:alpha4
parseplatform:parse-server9.6.0:alpha5
parseplatform:parse-server9.6.0:alpha6
parseplatform:parse-server9.6.0:alpha7
parseplatform:parse-server9.6.0:alpha8
parseplatform:parse-server9.6.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-69xg-f649-w5g2npmparse-server>=9.0.0 <9.6.0-alpha.139.6.0-alpha.13
GHSA-69xg-f649-w5g2npmparse-server>=8.0.2 <8.6.398.6.39

References

Check your stackJSON