CVE-2026-30228

Description

### Impact The `readOnlyMasterKey` can be used to create and delete files via the Files API (`POST /files/:filename`, `DELETE /files/:filename`). This bypasses the read-only restriction which violates the access scope of the `readOnlyMasterKey`. Any Parse Server deployment that uses `readOnlyMasterKey` and exposes the Files API is affected. An attacker with access to the `readOnlyMasterKey` can upload arbitrary files or delete existing files. ### Patches The fix adds permission checks to both the file upload and file delete handlers. ### Workarounds There is no workaround other than not using `readOnlyMasterKey`, or restricting network access to the Files API endpoints. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-xfh7-phr7-gr2x - Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.3 - Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.5

How to fix CVE-2026-30228

To remediate CVE-2026-30228, upgrade the affected package to a fixed version below.

• —upgrade to 9.5.0 or later
• —upgrade to 9.5.0-alpha.3 or later

Is CVE-2026-30228 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 9.5.0
• >= 9.0.0, < 9.5.0-alpha.3

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-30228
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.5
• WEBgithub.com/parse-community/parse-server/releases/tag/9.5.0-alpha.3