Vulnerability in parse-server (CVE-2026-53726)
Summary
Vulnerability in parse-server (CVE-2026-53726). Risk of unauthorized operations or information disclosure. Exploitable via Relation. Mitigation: upgrade to 8.6.80 or later.
Original description
The description as published by the source.
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.80 and 9.9.1-alpha.6, a relation query using the $relatedTo operator could read the membership of a Relation field even when that field was hidden from the requesting client by protectedFields, and even when the object owning the relation was not readable by the client under its ACL or class-level permissions. The request requires only the public API credentials that Parse clients normally carry — no user session, master key, or Cloud Code is needed. As a result, an unauthenticated client who knows or obtains the owning object's objectId could enumerate the objects linked through a protected relation, or combine the operator with an objectId constraint to use it as a membership oracle — confirming whether a specific object is linked to a private parent. This affects applications that rely on protectedFields or object ACLs to keep Relation membership confidential, such as private group memberships, block lists, or account-to-resource associations. This issue has been patched in versions 8.6.80 and 9.9.1-alpha.6.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53726 has been found in parse-server.
Attackers can target a specific entry point like Relation over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade parse-server to 8.6.80 or later.
If unsure, ask your IT team or search "parse-server CVE-2026-53726" on the vendor's site.
CVE-2026-53726 (parse-server) — CWE-639
Attack surface: Relation / protectedFields / objectId / beforeFind
Patched: 8.6.80 — apply immediately
Workaround: There is no complete workaround without upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in parse-server. Attackers reach the vulnerable code path via Relation.
Check the vendor advisory for the affected versions of parse-server. Attack surface: Relation / protectedFields / objectId / beforeFind.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.6.80.
Workaround: There is no complete workaround without upgrading.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'parse-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'parse-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
parse-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no complete workaround without upgrading.パッチが適用されるまでの応急処置として、There is no complete workaround without upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade parse-server to 8.6.80ステージング環境で 8.6.80 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com