Skip to main content
VulnerabilityPublished Updated

CVE-2026-30850: parse-server · Missing Authorization

Affects parse-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 9.5.0-alpha.9 or 8.6.9 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.5.0-alpha.9, 8.6.9
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade parse-server to 9.5.0-alpha.9 or 8.6.9; parse-community/parse-server to 8.6.9.

Affected software

ProductAffectedFixed in
parse-communityparse-serverAffected
  • <9.5.0-alpha.9
Fixed in
  • 9.5.0-alpha.9
parse-communityparse-serverAffected
  • <8.6.9
Fixed in
  • 8.6.9
npmparse-community/parse-serverpkg:npm/parse-community/parse-serverOther threatsAffected
  • <8.6.9
  • =9.5.0-alpha.9
Fixed in
  • 8.6.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade parse-server to version 8.6.9 or later, or 9.5.0-alpha.9 or later, where this vulnerability is patched. If upgrading is not immediately feasible, implement network-level access controls to restrict access to the file metadata endpoint to trusted users or internal networks only. Review and audit all beforeFind and afterFind triggers to ensure they are correctly applied and enforced across all relevant endpoints, including metadata retrieval. Employ logging and monitoring on file metadata access to detect unusual or unauthorized queries. Consider implementing additional application-layer authorization checks as a defense-in-depth measure. Finally, educate development teams about the importance of consistent trigger enforcement and authorization checks on all API endpoints to prevent similar issues.

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.9 and 9.5.0-alpha.9, the file metadata endpoint (GET /files/:appId/metadata/:filename) does not enforce beforeFind / afterFind file triggers. When these triggers are used as access-control gates, the metadata endpoint bypasses them entirely, allowing unauthorized access to file metadata. This issue has been patched in versions 8.6.9 and 9.5.0-alpha.9.

References

Community reviews

Loading reviews…