Summary
Parser Server's streaming file download bypasses afterFind file trigger authorization
Workarounds
Use beforeFind(Parse.File) instead of afterFind(Parse.File) for file access authorization. The beforeFind trigger runs on all download paths including streaming.
Impact
File downloads via HTTP Range requests bypass the afterFind(Parse.File) trigger and its validators on storage adapters that support streaming (e.g. the default GridFS adapter). This allows access to files that should be protected by afterFind trigger authorization logic or built-in validators such as requireUser.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The streaming file download path now executes the afterFind(Parse.File) trigger before sending any data. Authentication is resolved from the session token header so that trigger validators can distinguish authenticated from unauthenticated requests.
Frequently Asked Questions
- What is CVE-2026-34784? CVE-2026-34784 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.1-alpha.1. It is fixed in 9.7.1-alpha.1, 8.6.71.
- Which versions of parse-server are affected by CVE-2026-34784? parse-server (npm) versions >= 9.0.0, < 9.7.1-alpha.1 is affected.
- Is there a fix for CVE-2026-34784? Yes. CVE-2026-34784 is fixed in 9.7.1-alpha.1, 8.6.71. Upgrade to this version or later.
- Is CVE-2026-34784 exploitable, and should I be worried? Whether CVE-2026-34784 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
- What actually determines whether CVE-2026-34784 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.
- How do I fix CVE-2026-34784?
- Upgrade
parse-serverto 9.7.1-alpha.1 or later - Upgrade
parse-serverto 8.6.71 or later
- Upgrade