cve.bz

CVE-2026-39381 parseplatform parse-server: Incorrect Authorization

5.3 mediumEPSS 0.2%Fix available

Medium (5.3) in parseplatform parse-server. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.75, 9.8.0-alpha.7.

On this page
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.8.0-alpha.7 and 8.6.75, 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. This vulnerability is fixed in 9.8.0-alpha.7 and 8.6.75.

Severity

CVSS 4.0

5.3 medium
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

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-39381 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-39381?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-39381?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-39381 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.75
parseplatform:parse-serverfrom 9.0.0 before 9.8.0
parseplatform:parse-server9.8.0:alpha1
parseplatform:parse-server9.8.0:alpha2
parseplatform:parse-server9.8.0:alpha3
parseplatform:parse-server9.8.0:alpha4
parseplatform:parse-server9.8.0:alpha5
parseplatform:parse-server9.8.0:alpha6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g4v2-qx3q-4p64npmparse-server>=9.0.0 <9.8.0-alpha.79.8.0-alpha.7
GHSA-g4v2-qx3q-4p64npmparse-server>=7.0.0 <8.6.758.6.75

References

Check your stackJSON