CVE-2026-50008: parse-server Server Option RouteAllowList Is Bypassable Vulnerability

MODERATE
Advisory Identifier: GHSA-p84r-h6rx-f2xr
Share
CWE-863
Published
Advisory Summary

CVE-2026-50008 is a MODERATE server option routeallowlist is bypassable vulnerability (CWE-863: Incorrect Authorization) affecting parse-server libraries in the npm ecosystem. The issue involves server option routeallowlist is bypassable through batch sub-requests. Remediation is available by upgrading affected packages to version 9.9.1-alpha.3.

CVE-2026-50008 at a Glance

CVE Identifier CVE-2026-50008
GHSA Identifier GHSA-p84r-h6rx-f2xr
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product parse-server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-50008

To remediate this vulnerability, upgrade all affected parse-server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.9.1-alpha.3 
npm install parse-server@9.9.1-alpha.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-50008, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of parse-server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.9.1-alpha.3), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In parse-server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact The `routeAllowList` server option restricts external client access to a configured list of REST API routes. The check is only enforced as Express middleware against the outer HTTP request URL, so the `/batch` handler dispatches each sub-request to the internal router without re-running the allow-list check. An external caller whose outer route matches `batch` can issue batch sub-requests to any REST API route that the operator omitted from the allow-list. Authentication, ACL, CLP, and other inner-route authorization controls still apply — only the operator-configured route firewall is bypassed. ### Patches `routeAllowList` is now re-enforced for each batch sub-request inside the batch handler before dispatch, mirroring the existing per-sub-request rate-limit enforcement pattern. The path-normalization and regex-match logic was extracted into a shared helper used by both the outer middleware and the batch handler. Master and maintenance keys bypass the per-sub-request check on the same terms as the outer middleware. ### Workarounds Operators who use `routeAllowList` and have allowlisted `batch` can mitigate without upgrading by explicitly including every inner route they intend to allow via batch in the allow-list (for example, `routeAllowList: ['batch', 'classes/Public.*', 'functions/allowedFunction']`). This approach makes those inner routes reachable as direct REST requests as well, so it is broader than the post-patch behavior, but it eliminates the bypass. Operators who do not configure `routeAllowList` are not affected. Parse Server v8 LTS is not affected because `routeAllowList` was introduced in v9.8.0.

CVE-2026-50008 Affected parse-server Versions

1 component(s)
Fixed Versions:
9.9.1-alpha.3
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm/parse-server
npm
≥ 9.8.0
< 9.9.1-alpha.3
9.9.1-alpha.3

References

GitHub Advisory / Wiki ADVISORY
https://github.com/parse-community/parse-server/security/advisories/GHSA-p84r-h6rx-f2xr
NVD — CVE-2026-50008 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-50008
parse-server Source Repository REPOSITORY
https://github.com/parse-community/parse-server/pull/10482
parse-server Source Repository REPOSITORY
https://github.com/parse-community/parse-server

Frequently Asked Questions

What is CVE-2026-50008?
CVE-2026-50008 is a security vulnerability in parse-server involving Server option routeAllowList is bypassable through batch sub-requests under CWE-863: Incorrect Authorization.
Which parse-server versions are affected?
Affected versions include releases prior to 9.9.1-alpha.3 across affected packages: parse-server.
What version fixes CVE-2026-50008?
Upgrading to 9.9.1-alpha.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.9.1-alpha.3. Upgrade your dependency to 9.9.1-alpha.3 or later.
What CWE is associated with CVE-2026-50008?
CVE-2026-50008 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check npm dependencies for CVE-2026-50008?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p84r-h6rx-f2xr",
  "modified" : "2026-06-19T19:34:41Z",
  "published" : "2026-06-19T19:34:41Z",
  "aliases" : [ "CVE-2026-50008" ],
  "summary" : "parse-server: Server option routeAllowList is bypassable through batch sub-requests",
  "details" : "### Impact\n\nThe `routeAllowList` server option restricts external client access to a configured list of REST API routes. The check is only enforced as Express middleware against the outer HTTP request URL, so the `/batch` handler dispatches each sub-request to the internal router without re-running the allow-list check. An external caller whose outer route matches `batch` can issue batch sub-requests to any REST API route that the operator omitted from the allow-list.\n\nAuthentication, ACL, CLP, and other inner-route authorization controls still apply — only the operator-configured route firewall is bypassed.\n\n### Patches\n\n`routeAllowList` is now re-enforced for each batch sub-request inside the batch handler before dispatch, mirroring the existing per-sub-request rate-limit enforcement pattern. The path-normalization and regex-match logic was extracted into a shared helper used by both the outer middleware and the batch handler. Master and maintenance keys bypass the per-sub-request check on the same terms as the outer middleware.\n\n### Workarounds\n\nOperators who use `routeAllowList` and have allowlisted `batch` can mitigate without upgrading by explicitly including every inner route they intend to allow via batch in the allow-list (for example, `routeAllowList: ['batch', 'classes/Public.*', 'functions/allowedFunction']`). This approach makes those inner routes reachable as direct REST requests as well, so it is broader than the post-patch behavior, but it eliminates the bypass.\n\nOperators who do not configure `routeAllowList` are not affected. Parse Server v8 LTS is not affected because `routeAllowList` was introduced in v9.8.0.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.8.0"
      }, {
        "fixed" : "9.9.1-alpha.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-p84r-h6rx-f2xr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-50008"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10482"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:34:41Z",
    "nvd_published_at" : "2026-06-12T19:16:29Z"
  }
}