GHSA-jc39-686j-wp6q

Parse Server's Session Update endpoint allows overwriting server-generated session fields

At a glance

Published
Updated
CVE
CVE-2026-33527
Aliases
BIT-parse-2026-33527
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Description

### 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

Affected packages

PackageVersions
npm · parse-serverintroduced 9.0.0, fixed 9.6.0-alpha.48
npm · parse-serverintroduced 0, fixed 8.6.57

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database