Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
### Impact The `ConfigKeyCache` uses the same cache key for both master key and read-only master key when resolving function-typed keys. Under specific timing conditions, a read-only user can receive the cached full master key, or a regular user can receive the cached read-only master key. ### Patches The fix uses distinct cache keys for master key and read-only master key. ### Workarounds Avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration. ### Resources - GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr - Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-27610US | medium5.3 | — | ||
Parse Dashboard is a standalone dashboard for managing Parse Server apps. In versions 7.3.0-alpha.42 through 9.0.0-alpha.7, the `ConfigKeyCache` uses the same cache key for both ma… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/parse-community/parse-dashboardPACKAGE
- https://github.com/parse-community/parse-dashboard/commit/f92a9ef5246d57e51696bd881a15f3b133b2bb50WEB
- https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8WEB
- https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xrWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-27610ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan