parse-community parse-server up to 8.6.38/9.6.0-alpha.12 Token Introspection Endpoint function call with incorrect order of arguments
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in parse-community parse-server up to 8.6.38/9.6.0-alpha.12. This vulnerability affects unknown code of the component Token Introspection Endpoint. Executing a manipulation can lead to function call with incorrect order of arguments. This vulnerability is tracked as CVE-2026-32269. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in parse-community parse-server up to 8.6.38/9.6.0-alpha.12. It has been declared as problematic. This vulnerability affects an unknown code block of the component Token Introspection Endpoint. The manipulation with an unknown input leads to a function call with incorrect order of arguments vulnerability. The CWE definition for the vulnerability is CWE-683. The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-32269 since 03/11/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 8.6.39 or 9.6.0-alpha.13 eliminates this vulnerability. The upgrade is hosted for download at github.com.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202603-2476). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 8.6.0
- 8.6.1
- 8.6.2
- 8.6.3
- 8.6.4
- 8.6.5
- 8.6.6
- 8.6.7
- 8.6.8
- 8.6.9
- 8.6.10
- 8.6.11
- 8.6.12
- 8.6.13
- 8.6.14
- 8.6.15
- 8.6.16
- 8.6.17
- 8.6.18
- 8.6.19
- 8.6.20
- 8.6.21
- 8.6.22
- 8.6.23
- 8.6.24
- 8.6.25
- 8.6.26
- 8.6.27
- 8.6.28
- 8.6.29
- 8.6.30
- 8.6.31
- 8.6.32
- 8.6.33
- 8.6.34
- 8.6.35
- 8.6.36
- 8.6.37
- 8.6.38
- 9.6.0-alpha.0
- 9.6.0-alpha.1
- 9.6.0-alpha.2
- 9.6.0-alpha.3
- 9.6.0-alpha.4
- 9.6.0-alpha.5
- 9.6.0-alpha.6
- 9.6.0-alpha.7
- 9.6.0-alpha.8
- 9.6.0-alpha.9
- 9.6.0-alpha.10
- 9.6.0-alpha.11
- 9.6.0-alpha.12
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Function call with incorrect order of argumentsCWE: CWE-683
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: parse-server 8.6.39/9.6.0-alpha.13
Timeline
03/11/2026 CVE reserved03/12/2026 Advisory disclosed
03/12/2026 VulDB entry created
03/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-69xg-f649-w5g2
Status: Confirmed
CVE: CVE-2026-32269 (🔒)
GCVE (CVE): GCVE-0-2026-32269
GCVE (VulDB): GCVE-100-350782
CNNVD: CNNVD-202603-2476 - Parse Server 安全漏洞
Entry
Created: 03/12/2026 21:58Updated: 03/15/2026 19:34
Changes: 03/12/2026 21:58 (68), 03/13/2026 15:00 (6), 03/14/2026 18:58 (1), 03/15/2026 04:37 (12), 03/15/2026 19:34 (1)
Complete: 🔍
Cache ID: 216:D86:103
No comments yet. Languages: en.
Please log in to comment.