GHSA-5v7g-9h8f-8pgg
Parse Server session creation endpoint allows overwriting server-generated session fields
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | parse-server | >= 9.0.0, < 9.6.0-alpha.17 | 9.6.0-alpha.17 |
| npm | parse-server | < 8.6.42 | 8.6.42 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
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.
### Patches
The session creation endpoint now filters out server-generated fields from user-supplied data, preventing them from being overwritten.
### Workarounds
Add a `beforeSave` trigger on the `_Session` class to validate and reject or strip any user-supplied values for `sessionToken`, `expiresAt`, and `createdWith`.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/parse-community/parse-server/security/advisories/GHSA-5v7g-9h8f-8pgg
- https://nvd.nist.gov/vuln/detail/CVE-2026-32742
- https://github.com/parse-community/parse-server/pull/10195
- https://github.com/parse-community/parse-server/pull/10196
- https://github.com/parse-community/parse-server