CVE-2026-30850

Workarounds

Disable the metadata endpoint by overriding the route with a middleware that rejects all requests:

// Add before mounting Parse Server
app.get('/parse/files/:appId/metadata/:filename', (req, res) => {
  res.status(403).json({ error: 'Forbidden' });
});

Adjust the path prefix (/parse) to match your mountPath.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hwx8-q9cg-mqmc
• Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.9
• Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.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 affects any deployment that relies on Parse.Cloud.beforeFind(Parse.File, ...) to restrict file access. Only file metadata (user-defined key-value pairs set via addMetadata) is exposed; file content remains protected.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Kodem intelligence

The metadata handler now runs beforeFind and afterFind triggers and returns HTTP 403 when a trigger denies access.

1. What is CVE-2026-30850? CVE-2026-30850 is a medium-severity missing authorization vulnerability in parse-server (npm), affecting versions < 8.6.9. It is fixed in 8.6.9, 9.5.0-alpha.9. The application does not perform an authorization check before performing a sensitive operation.
2. Which versions of parse-server are affected by CVE-2026-30850? parse-server (npm) versions < 8.6.9 is affected.
3. Is there a fix for CVE-2026-30850? Yes. CVE-2026-30850 is fixed in 8.6.9, 9.5.0-alpha.9. Upgrade to this version or later.
4. Is CVE-2026-30850 exploitable, and should I be worried? Whether CVE-2026-30850 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
5. What actually determines whether CVE-2026-30850 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.
6. How do I fix CVE-2026-30850?
   • Upgrade parse-server to 8.6.9 or later
   • Upgrade parse-server to 9.5.0-alpha.9 or later

Other vulnerabilities in parse-server