GHSA-g4v2-qx3q-4p64
Parse Server's Endpoint `/sessions/me` bypasses `_Session` `protectedFields`
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | parse-server | >= 9.0.0, < 9.8.0-alpha.7 | 9.8.0-alpha.7 |
| npm | parse-server | >= 7.0.0, < 8.6.75 | 8.6.75 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
The `GET /sessions/me` endpoint returns `_Session` fields that the server operator explicitly configured as protected via the `protectedFields` server option. Any authenticated user can retrieve their own session's protected fields with a single request. The equivalent `GET /sessions` and `GET /sessions/:objectId` endpoints correctly strip protected fields.
### Patches
The `GET /sessions/me` handler now re-fetches the session with the caller's auth context after validating the session token, ensuring `protectedFields` and CLP apply consistently with other session endpoints.
### Workarounds
None.
### References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-g4v2-qx3q-4p64
- Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10406
- Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10407
References
External links from the advisory. They lead to third-party sites.
- https://github.com/parse-community/parse-server/security/advisories/GHSA-g4v2-qx3q-4p64
- https://nvd.nist.gov/vuln/detail/CVE-2026-39381
- https://github.com/parse-community/parse-server/pull/10406
- https://github.com/parse-community/parse-server/pull/10407
- https://github.com/parse-community/parse-server