GitHub Advisoryadvisory · npm
GHSA-g4v2-qx3q-4p64 Parse Server's Endpoint `/sessions/me` bypasses `_Session` `protectedFields`
MEDIUM
Official page ↗
- Aliases
- CVE-2026-39381
- Ecosystem
- npm
- Packages
- parse-server
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-863
- Reviewed
- 2026-04-08
Affected packages
• npm parse-server: >= 9.0.0, < 9.8.0-alpha.7 → fixed in 9.8.0-alpha.7
• npm parse-server: >= 7.0.0, < 8.6.75 → fixed in 8.6.75
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
Related
Alias · CVE (1)
- CVE-2026-39381 Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. vulnerability
Weakness · CWE (1)
- CWE-863 Incorrect Authorization weakness
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-g4v2-qx3q-4p64 web
- https://nvd.nist.gov/vuln/detail/CVE-2026-39381 advisory
- https://github.com/parse-community/parse-server/pull/10406 web
- https://github.com/parse-community/parse-server/pull/10407 web
- https://github.com/parse-community/parse-server package