CVE-2026-39381

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

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-39381 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.8.0-alpha.7, 8.6.75); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-39381? CVE-2026-39381 is a medium-severity incorrect authorization vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.8.0-alpha.7. It is fixed in 9.8.0-alpha.7, 8.6.75. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-39381? CVE-2026-39381 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of parse-server are affected by CVE-2026-39381? parse-server (npm) versions >= 9.0.0, < 9.8.0-alpha.7 is affected.
4. Is there a fix for CVE-2026-39381? Yes. CVE-2026-39381 is fixed in 9.8.0-alpha.7, 8.6.75. Upgrade to this version or later.
5. Is CVE-2026-39381 exploitable, and should I be worried? Whether CVE-2026-39381 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-39381 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-39381?
   • Upgrade parse-server to 9.8.0-alpha.7 or later
   • Upgrade parse-server to 8.6.75 or later