GHSA-jc39-686j-wp6q
Parse Server's Session Update endpoint allows overwriting server-generated session fields
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | parse-server | >= 9.0.0, < 9.6.0-alpha.48 | 9.6.0-alpha.48 |
| npm | parse-server | < 8.6.57 | 8.6.57 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
An authenticated user can overwrite server-generated session fields such as `expiresAt` and `createdWith` when updating their own session via the REST API. This allows bypassing the server's configured session lifetime policy, making a session effectively permanent.
### Patches
The fix blocks authenticated users from setting `expiresAt` and `createdWith` fields when updating a session. Master key and maintenance key operations are not affected.
### Workarounds
There is no known workaround other than upgrading.
### Resources
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-jc39-686j-wp6q
- Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10263
- Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10264
References
External links from the advisory. They lead to third-party sites.
- https://github.com/parse-community/parse-server/security/advisories/GHSA-jc39-686j-wp6q
- https://nvd.nist.gov/vuln/detail/CVE-2026-33527
- https://github.com/parse-community/parse-server/pull/10263
- https://github.com/parse-community/parse-server/pull/10264
- https://github.com/parse-community/parse-server/commit/26b628c8fb3cc79ea955374769eebcff6f8a8a73
- https://github.com/parse-community/parse-server/commit/ea68fc0b22a6056c9675149469ff57817f7cf984
- https://github.com/parse-community/parse-server