CVE-2026-27610
published 2026-02-25CVE-2026-27610: 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…
PriorityP432medium5.3CVSS 3.1
AVNACHPRLUINSUCHINAN
EPSS
0.34%
25.5th percentile
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 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. The fix in version 9.0.0-alpha.8 uses distinct cache keys for master key and read-only master key. As a workaround, avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.
Affected
137 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| parse-community | parse-dashboard | — | — |
| parse-community | parse-dashboard | >= 7.3.0-alpha.42 < 9.0.0-alpha.8 | 9.0.0-alpha.8 |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
| parseplatform | parse_dashboard | — | — |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv4.07.0HIGHCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
osv·2026-02-25
CVE-2026-27610 [HIGH] Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
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/
GHSA
Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
ghsa·2026-02-25
CVE-2026-27610 [HIGH] CWE-1289 Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
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/
No detection rules found.
No public exploits indexed.
2026-02-25
Published