External risk intelligence

Parse Server Cloud Function Access Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-34532

Parse Server is commonly deployed as an internet-facing backend application or API framework. Because it serves as the primary interface for applications to interact with their data and cloud functions, it is routinely exposed as an external web service.

Parseplatform Parse Server

before 8.6.679.0.0 to before 9.7.09.7.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in Parse Server, an open-source backend technology used in various applications. This issue allows unauthenticated attackers to bypass access controls for Cloud Functions, potentially enabling unauthorized invocation of sensitive operations. The main concern is confirming relevance and exposure within our deployed Parse Server instances.

  • Attackers can bypass Cloud Function security.
  • Protects sensitive data and operations access.
  • Confirm relevance and exposure in Parse Server.

Attack Path

How an attacker could exploit the issue

An attacker can target Parse Server by manipulating Cloud Function URLs to bypass security checks. This is achieved by appending "prototype.constructor" to a function's name in the URL, which tricks the server into executing protected functions without proper validation. This bypass allows unauthorized access to sensitive operations.

  • Attacker sends crafted URL.
  • Vulnerable Cloud Function bypasses validation.
  • Unauthenticated access to protected functions.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, unauthenticated callers could invoke protected Cloud Functions, potentially affecting system data and service behavior. This bypasses intended access controls, allowing unauthorized execution of sensitive operations.

  • Protected Cloud Functions.
  • Appending to function name in URL.
  • Unauthorized operation execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

The primary teams responsible for addressing this vulnerability are likely application owners and platform teams who manage Parse Server deployments, along with network or security teams responsible for securing external-facing services. The immediate practical action is to identify all Parse Server instances, determine their exposure and business criticality, and then coordinate remediation with the accountable owners, potentially involving vendor management if Parse Server was procured externally.

  • Application and platform owners should investigate.
  • Verify Parse Server instances and exposure levels.
  • Plan risk-based remediation or vendor engagement.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Parse Server and what is it used for?

Parse Server is an open-source backend framework that developers deploy on Node.js infrastructure. It acts as a central hub for applications, managing data storage, user authentication, and executing server-side logic called Cloud Functions, which perform specific tasks or operations on behalf of the application.

What is the vulnerability in CVE-2026-34532?

This flaw is an incorrect authorization issue, categorized as CWE-863. It occurs when the server's internal logic fails to correctly check access permissions for Cloud Functions. Because of how the server resolves function names, it can be tricked into skipping security validators, allowing unauthorized users to execute functions that should have been restricted.

How do attackers trigger this bypass?

An attacker triggers this by appending the string "prototype.constructor" to the name of a Cloud Function within the request URL. This specifically impacts Cloud Functions defined with the function keyword using certain validator types. Importantly, functions that do not rely on these specific validator configurations or are not reachable via manipulated URLs are not subject to this bypass path.

Is my Parse Server deployment at risk?

Halo Surface Signal indicates this vulnerability is highly relevant for most users because Parse Server is typically deployed as an internet-facing API gateway. If your instance exposes Cloud Functions to the public internet, it is a likely target for this bypass. Instances restricted entirely to internal-only networks face a lower profile but still require attention.

What steps should I take to fix this?

The primary response is to update your Parse Server installation to version 8.6.67 or 9.7.0-alpha.11 or higher, where this flaw is patched. Before updating, identify all your active Parse Server instances to ensure complete coverage. If you manage these as part of a platform team, coordinate with application owners to schedule the deployment of these versions to restore proper access control enforcement.

References