CVE-2026-30850
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedParse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.9 and 9.5.0-alpha.9, the 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. This issue has been patched in versions 8.6.9 and 9.5.0-alpha.9.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceParse Server's file metadata endpoint (GET /files/:appId/metadata/:filename) fails to enforce beforeFind and afterFind file triggers. When these triggers are used as access-control mechanisms, the metadata endpoint bypasses them entirely, allowing unauthorized access to file metadata.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.6.9>= 9.0.0, < 9.5.0= 9.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Parse Server versionRun 'npm list parse-server' or check your package.json to determine the installed version of parse-serverAffected if Version is less than 8.6.9, or between 9.0.0 and 9.5.0 (inclusive), or exactly 9.5.0
-
Identify if file triggers are configuredExamine your cloud code (cloud/main.js) or trigger configuration files for beforeFind or afterFind triggers defined for the 'Files' classAffected if File triggers (beforeFind or afterFind for Files class) are defined and used as an access-control mechanism
-
Verify metadata endpoint is exposedCheck if the Parse Server is running and the /files/:appId/metadata/:filename endpoint is accessible (check server.js or express routes configuration for parse-server mount path)Affected if The metadata endpoint is accessible without additional authentication beyond the Parse Server basic authentication
-
Confirm trigger bypass conditionTest making a metadata request to /files/:appId/metadata/:filename directly - if the request succeeds without the file triggers being executed, the bypass existsAffected if Metadata endpoint returns data without triggering beforeFind or afterFind cloud code hooks
You are affected if your Parse Server version falls within the vulnerable range AND you rely on file triggers for access control, as the metadata endpoint bypasses these triggers entirely.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.6.99.5.0
Upgrade Parse Server to version 8.6.9 or higher (or 9.5.0-alpha.9 for alpha releases) to apply the patch that enforces trigger execution on the metadata endpoint.
Upgrade to Parse Server 8.6.9 (stable) or 9.5.0+ (if available)
- 1. Identify your current Parse Server version using `npm list parse-server` or checking your package.json
- 2. For Parse Server versions < 8.6.9: Upgrade to version 8.6.9 by running `npm install [email protected]` or updating the version in package.json
- 3. For Parse Server versions >= 9.0.0 and <= 9.5.0: Upgrade to version 9.5.0 or later (if available) by running `npm install parse-server@latest` or specifying a version >= 9.5.1
- 4. After upgrading, test the file metadata endpoint (GET /files/:appId/metadata/:filename) to confirm triggers are now enforced
- 5. Verify that existing beforeFind and afterFind file triggers are functioning correctly for the metadata endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30850 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data