CVE-2026-119571: Parse Server 9.7.0 before 9.10.5 Installation Update Misdirection via Installation ID
Parse Server from 9.7.0 before 9.10.5 contains an authorization flaw that applies Installation updates addressed by object ID to the installation named in the X-Parse-Installation-Id header. When protectedFieldsTriggerExempt is enabled, attackers knowing another installation's object ID can make a beforeSave trigger process that installation's protected fields while writing elsewhere.
Other sources
Parse Server from 9.7.0 before 9.10.5-alpha.10 contains an authorization flaw that applies Installation updates addressed by object ID to the installation named in the X-Parse-Installation-Id header. When protectedFieldsTriggerExempt is enabled, attackers knowing another installation's object ID can make a beforeSave trigger process that installation's protected fields while writing elsewhere.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
bitnami/parseto a version that resolves this vulnerability.Fixed in 9.10.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.10.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.10.5-alpha.10
Event History
Frequently Asked Questions
Which deployments are affected?
Parse Server versions from 9.7.0 up to, but not including, 9.10.5-alpha.10 are affected when protectedFieldsTriggerExempt is enabled.
What does an attacker need to exploit this issue?
An attacker needs to know the object ID of another installation. No privileges or user interaction are required, but exploitation has high attack complexity.
What is the impact of a successful exploit?
A beforeSave trigger can be made to process protected fields belonging to the targeted installation while the update is written to a different installation. The reported impact is limited to confidentiality; integrity and availability are not affected.
How can I determine whether I may be exposed?
Check whether your Parse Server version is within the affected range and whether protectedFieldsTriggerExempt is enabled. Also review whether beforeSave triggers process protected Installation fields, as that is the condition described for the misdirection.