parse-community/parse-server · Security
Parse Server's Endpoint `/sessions/me` bypasses `_Session` `protectedFields`
- GHSA ID
- GHSA-g4v2-qx3q-4p64
- CVE ID
- CVE-2026-39381
- Severity
- medium
- Published
- Updated
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CVSS v3
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CVSS v4
- 5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Description
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
CWEs
- CWE-863 · Incorrect Authorization
References
- 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/advisories/GHSA-g4v2-qx3q-4p64 ↗