CVE-2026-30228

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

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

The fix adds permission checks to both the file upload and file delete handlers.

1. What is CVE-2026-30228? CVE-2026-30228 is a medium-severity incorrect authorization vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.5.0-alpha.3. It is fixed in 9.5.0-alpha.3, 8.6.5. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which versions of parse-server are affected by CVE-2026-30228? parse-server (npm) versions >= 9.0.0, < 9.5.0-alpha.3 is affected.
3. Is there a fix for CVE-2026-30228? Yes. CVE-2026-30228 is fixed in 9.5.0-alpha.3, 8.6.5. Upgrade to this version or later.
4. Is CVE-2026-30228 exploitable, and should I be worried? Whether CVE-2026-30228 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-30228 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-30228?
   • Upgrade parse-server to 9.5.0-alpha.3 or later
   • Upgrade parse-server to 8.6.5 or later

Other vulnerabilities in parse-server