Parse Server data corruption via dot notation field writes
parse-community parse-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| parse-community parse-server |
|
|
| parse-community parse-server |
|
|
Original description
Parse Server before 8.6.111 and 9.0.0 before 9.10.6-alpha.3 on MongoDB skips field type validation for null-valued dot notation keys, allowing sub-documents to be written beneath Pointer, Number, String, Date, or Boolean fields. Any client with write access, including unauthenticated clients where public writes are permitted, can corrupt field values, make objects unreadable via internal date fields, or break atomic operations on number fields.
From the CVE record · VulnCheck
References
- github.com/parse-community/parse-server/security/advisories/GHSA-655c-2xf3-77x9
- github.com/parse-community/parse-server/pull/10804Patch
- github.com/parse-community/parse-server/pull/10805Patch
- vulncheck.com/advisories/parse-server-before-8.6.111-and-9.0.0-before-9.10.6-alpha.3-field-corruption-via-null-dot-notation-key
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/121xxx/CVE-2026-121415.json
- nvd.nist.gov/vuln/detail/CVE-2026-121415