GHSA-f6j3-w9v3-cq22
Parse Server has a session field immutability bypass via falsy-value guard
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | parse-server | >= 9.0.0, < 9.7.0-alpha.14 | 9.7.0-alpha.14 |
| npm | parse-server | < 8.6.69 | 8.6.69 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
An authenticated user can bypass the immutability guard on session fields (`expiresAt`, `createdWith`) by sending a null value in a PUT request to the session update endpoint. This allows nullifying the session expiry, making the session valid indefinitely and bypassing configured session length policies.
### Patches
The truthiness-based guard checks were replaced with key-presence checks that reject any value for protected session fields, including null.
### Workarounds
There is no known workaround. A `beforeSave` trigger on `_Session` could be used to reject null values for `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-f6j3-w9v3-cq22
- https://nvd.nist.gov/vuln/detail/CVE-2026-34574
- https://github.com/parse-community/parse-server/pull/10347
- https://github.com/parse-community/parse-server/pull/10348
- https://github.com/parse-community/parse-server/commit/90802969fc713b7bc9733d7255c7519a6ed75d21
- https://github.com/parse-community/parse-server/commit/ebccd7fe2708007e62f705ee1c820a6766178777
- https://github.com/parse-community/parse-server