CVE-2026-39381

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

How to fix CVE-2026-39381

To remediate CVE-2026-39381, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.75 or later
• —upgrade to 9.8.0-alpha.7 or later

Is CVE-2026-39381 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• >= 7.0.0, < 8.6.75, >= 9.0.0, < 9.8.0
• >= 9.0.0, < 9.8.0-alpha.7

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-39381
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/pull/10406
• WEBgithub.com/parse-community/parse-server/pull/10407