CVE-2026-30850: Parse Server File Metadata Endpoint Bypasses `beforeFind` Vulnerability
MODERATECVE-2026-30850 is a MODERATE file metadata endpoint bypasses `beforefind` vulnerability (CWE-862: Missing Authorization) affecting Parse Server libraries in the npm ecosystem. The issue involves file metadata endpoint bypasses `beforefind` / `afterfind` trigger authorization. Remediation is available by upgrading affected packages to version 8.6.9, 9.5.0-alpha.9.
CVE-2026-30850 at a Glance
How to Fix CVE-2026-30850
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.
npm install parse-server@8.6.9
npm install parse-server@9.5.0-alpha.9
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-30850, 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 8.6.9), 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-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. 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
CVE-2026-30850 Affected Parse Server Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
parse-server
|
npm |
< 8.6.9
|
8.6.9
|
|
parse-server
|
npm |
≥ 9.0.0-alpha.1
< 9.5.0-alpha.9
|
9.5.0-alpha.9
|
References
Frequently Asked Questions
What is CVE-2026-30850?
Which Parse Server versions are affected?
What version fixes CVE-2026-30850?
Is parse-server affected?
What CWE is associated with CVE-2026-30850?
How can I check npm dependencies for CVE-2026-30850?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hwx8-q9cg-mqmc",
"modified" : "2026-03-09T17:42:03Z",
"published" : "2026-03-09T17:42:03Z",
"aliases" : [ "CVE-2026-30850" ],
"summary" : "Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization",
"details" : "### Impact\n\nThe 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.\n\nThis 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.\n\n### Patches\n\nThe metadata handler now runs `beforeFind` and `afterFind` triggers and returns HTTP 403 when a trigger denies access.\n\n### Workarounds\n\nDisable the `metadata` endpoint by overriding the route with a middleware that rejects all requests:\n\n```js\n// Add before mounting Parse Server\napp.get('/parse/files/:appId/metadata/:filename', (req, res) => {\n res.status(403).json({ error: 'Forbidden' });\n});\n```\n\nAdjust the path prefix (`/parse`) to match your mountPath.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hwx8-q9cg-mqmc\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.9\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.9",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "8.6.9"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "parse-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0-alpha.1"
}, {
"fixed" : "9.5.0-alpha.9"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-hwx8-q9cg-mqmc"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30850"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/parse-community/parse-server"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-862" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-09T17:42:03Z",
"nvd_published_at" : "2026-03-07T17:15:52Z"
}
}