/

CVE-2026-34784

Severity:

HIGH RISK

(7.5)

Authorization Bypass in Parse Server Streaming Adapters

CVE-2026-34784

Analyzed

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285

Impact:

Unauthorized Access to Protected Files

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Parse Server contains an authorization bypass that allows HTTP Range-based file downloads to skip the afterFind(Parse.File) trigger and related validators on streaming-capable storage adapters.

When Range requests are used against adapters like the default GridFS adapter, files intended to be protected by trigger-based access control or validators (such as requireUser) can be accessed without proper authorization checks.

Affected context

The vulnerability appears in Parse Server deployments that:

  • Use storage adapters supporting streaming file downloads (for example, the default GridFS adapter),
  • Rely on afterFind(Parse.File) triggers or built-in validators (such as requireUser) to enforce access control on files, and
  • Expose file download endpoints that accept HTTP Range headers.

In such environments, the Range-based code path for file downloads does not consistently invoke the same authorization logic as regular file retrieval.

Exploit preconditions

  • Attack surface: Public or internal HTTP(S) endpoints that serve Parse Server file downloads.
  • Required access: Ability to send crafted HTTP requests to the file download endpoint; knowledge or ability to guess file identifiers/URLs.
  • Trigger point: Issuing HTTP requests that include a Range header to download files through streaming adapters.
  • Why exploitation is possible: The streaming download path for Range requests bypasses the afterFind(Parse.File) trigger and associated validators, so authorization logic that would normally restrict access is not applied to these requests.

Why this happens

The root cause is an inconsistent application of authorization logic across different file download paths.

While standard file retrieval routes invoke the afterFind(Parse.File) trigger and built-in validators, the streaming code path used for HTTP Range requests does not.

This discrepancy creates an authorization bypass scenario mapped to CWE-285: Improper Authorization, where protection mechanisms exist but are not uniformly enforced for all relevant operations.

Conceptually, the system treats Range-based streaming as a lower-level I/O operation and fails to reapply higher-level access control policies before serving file content.

Potential impact

  • Unauthorized reading of files that should be protected by trigger-based access control.
  • Exposure of sensitive user-generated content or private application assets.
  • Circumvention of requireUser or similar validators that normally restrict file access.
  • Potential leakage of PII or confidential business data stored as files in Parse Server.

General mitigation guidance

Effective mitigation focuses on consistent enforcement of authorization for all file access paths and on reducing reliance on trigger-only controls:

  • Ensure that all file download mechanisms, including streaming and Range-based responses, pass through a unified authorization layer before serving content.
  • Design access control so that policy decisions are applied close to the storage abstraction rather than relying solely on high-level triggers.
  • Prefer explicit, declarative authorization rules for files (e.g., ACLs, role-based checks) that are evaluated regardless of transport mechanism or HTTP headers.
  • Minimize direct exposure of raw file URLs without an application-layer guard that verifies user identity and permissions.
  • Apply least-privilege principles at the storage layer, restricting generic read access from untrusted code paths.

These patterns help ensure that new adapters or transport features cannot accidentally bypass existing access control logic.

How teams detect issues like this

Detection can leverage both code-level and behavior-level analysis:

  • Static analysis & code review:
  • Look for file-serving code paths that handle HTTP Range headers or streaming responses and verify that they invoke the same authorization routines as standard downloads.
  • Check adapters and middleware for early-return paths that stream file data without passing through centralized access control checks.
  • Review usage of afterFind(Parse.File) triggers and confirm whether any alternative retrieval methods bypass these triggers.
  • Runtime & logging strategies:
  • Enable detailed access logs for file downloads, including headers and user context, and flag Range-based requests that successfully return content without an authenticated user.
  • Monitor for high volumes of partial-content (206) responses to files that are expected to be restricted.
  • Security testing:
  • Incorporate HTTP Range variations into API tests and authorization test suites, verifying that every file access method requires appropriate permissions.

Automated security review tools or custom linters can be configured to highlight direct streaming reads from storage that are not preceded by explicit authorization checks.

Sources

SourceLink
github.comgithub.com/parse-community/parse-server/commit/053109b3ee71815bc39ed84116c108ff9edbf337
github.comgithub.com/parse-community/parse-server/commit/a0b0c69fc44f87f80d793d257344e7dcbf676e22
github.comgithub.com/parse-community/parse-server/pull/10361
github.comgithub.com/parse-community/parse-server/pull/10362
github.comgithub.com/parse-community/parse-server/security/advisories/GHSA-hpm8-9qx6-jvwv

Frequently asked

questions

Yes. An attacker who can reach the Parse Server file download endpoint over the network and knows or can guess file URLs or identifiers can attempt to exploit the vulnerability using crafted HTTP Range requests.

The attacker generally needs only network access to the file download endpoint; explicit authentication may not be required if the endpoint is reachable and relies on triggers or validators for protection. If protected files are identifiable or guessable, they may be retrieved without proper authorization.

The most robust fix is to centralize file access control so that every download path—standard, streaming, and Range-based—passes through the same authorization checks, independent of HTTP headers or adapter implementations. Avoid maintaining separate or optional code paths that can serve file content without revalidating permissions.

Treat access control as a cross-cutting concern applied at a single, authoritative layer. During design and code review, verify that any new feature (such as streaming or partial content support) reuses existing authorization mechanisms. Complement this with automated tests specifically targeting alternate protocols and headers (like Range) to ensure consistent enforcement of file access policies.

Find out what's already
exploitable in your codebase.