CVE-2026-32742 json
Parse Server session creation endpoint allows overwriting server-generated session fields
published 2026-03-17 7 mo ago modified 2026-09-08 2 mo ago also BIT-parse-2026-32742 , EUVD-2026-12983 , GHSA-5v7g-9h8f-8pgg
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.17 and 8.6.42, an authenticated user can overwrite server-generated session fields (`sessionToken`, `expiresAt`, `createdWith`) when creating a session object via `POST /classes/_Session`. This allows bypassing the server's session expiration policy by setting an arbitrary far-future expiration date. It also allows setting a predictable session token value. Starting in version 9.6.0-alpha.17 and 8.6.42, the session creation endpoint filters out server-generated fields from user-supplied data, preventing them from being overwritten. As a workaround, add a `beforeSave` trigger on the `_Session` class to validate and reject or strip any user-supplied values for `sessionToken`, `expiresAt`, and `createdWith`.
Patch / fix
- npm parse-server 8.6.42, 9.6.0-alpha.17
- bitnami parse 8.6.42, 9.6.0
- parseplatform parse-server 8.6.42, 9.6.0-alpha.17
- parseplatform parse_server 8.6.42, 9.6.0-alpha.17
- github.com/parse-community/parse-server#10195 pull request
- github.com/parse-community/parse-server#10196 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=9.0.0, <9.6.0-alpha.17 <8.6.42 |
9.6.0-alpha.17 8.6.42 |
| bitnami | parse | <8.6.42 >=9.0.0, <9.6.0 |
8.6.42 9.6.0 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
References
-
github.com
/parse-community/parse-server/pull/10195
web, issue-tracking, report
-
github.com
/parse-community/parse-server/pull/10196
web, issue-tracking, report
-
github.com
/parse-community/parse-server/security/advisories/GHSA-5v7g-9h8f-8pgg
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-32742
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2026-32742
- GitHub Advisory GHSA-5v7g-9h8f-8pgg
- NVD CVE-2026-32742
- OSV BIT-parse-2026-32742
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.