GHSA-jc39-686j-wp6q
Parse Server's Session Update endpoint allows overwriting server-generated session fields
Details
### 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
Are you affected?
Enter the version of the package you're using.
Affected packages
9.0.0 Fixed in: 9.6.0-alpha.48 npm install parse-server@9.6.0-alpha.48 References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-jc39-686j-wp6q [WEB]
- https://nvd.nist.gov/vuln/detail/CVE-2026-33527 [ADVISORY]
- https://github.com/parse-community/parse-server/pull/10263 [WEB]
- https://github.com/parse-community/parse-server/pull/10264 [WEB]
- https://github.com/parse-community/parse-server/commit/26b628c8fb3cc79ea955374769eebcff6f8a8a73 [WEB]
- https://github.com/parse-community/parse-server/commit/ea68fc0b22a6056c9675149469ff57817f7cf984 [WEB]
- https://github.com/parse-community/parse-server [PACKAGE]