Advisory

GHSA-xfh7-phr7-gr2x

Also known as: BIT-parse-2026-30228, CVE-2026-30228

Summary

parse-server's file creation and deletion bypasses readOnlyMasterKey write restriction

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-06 18:45 UTC
Modified
2026-03-16 03:04 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.5.0-alpha.3 (semver)

Fixed versions

9.5.0-alpha.3

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.5 (semver)

Fixed versions

8.6.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences