{"id":"CVE-2026-27610","aliases":["EUVD-2026-8593","GHSA-jhp4-jvq3-w5xr"],"status":"published","title":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","description":"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.","severity":{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00383,"percentile":0.32862,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1289"],"published":"2026-02-25T02:19:56Z","modified":"2026-10-28T02:31:04Z","fixes":[{"ecosystem":"npm","package":"parse-dashboard","fixed_in":["9.0.0-alpha.8"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"parse-dashboard","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.3.0-alpha.42"},{"fixed":"9.0.0-alpha.8"}]}]},{"source":"osv","ecosystem":"npm","package":"parse-dashboard","ranges":[{"type":"SEMVER","events":[{"introduced":"7.3.0-alpha.42"},{"fixed":"9.0.0-alpha.8"}]}]}],"products":[{"vendor":"parse-community","product":"parse-dashboard"},{"vendor":"parseplatform","product":"parse_dashboard"}],"references":[{"url":"https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory","web"]},{"url":"https://github.com/parse-community/parse-dashboard/commit/f92a9ef5246d57e51696bd881a15f3b133b2bb50","tags":["x_refsource_MISC","Patch","fix","web"]},{"url":"https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8","tags":["x_refsource_MISC","Release Notes","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-27610","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-jhp4-jvq3-w5xr"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27610.json","tags":["advisory"]},{"url":"https://github.com/parse-community/parse-dashboard","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-27610","title":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","description":"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.","status":"published","published":"2026-02-25T02:19:56.022Z","modified":"2026-02-27T17:24:10.098Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high","assessor":"cna"}],"cwes":["CWE-1289"],"updated_at":"2026-11-02T14:19:48.826324Z"}],"euvd":[{"id":"EUVD-2026-8593","description":"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.","status":"published","published":"2026-02-25T02:19:56Z","modified":"2026-02-27T17:24:10Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high"}],"updated_at":"2026-11-02T19:48:13.609806Z"}],"ghsa":[{"id":"GHSA-jhp4-jvq3-w5xr","title":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","description":"### Impact\n\nThe `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.\n\n### Patches\n\nThe fix uses distinct cache keys for master key and read-only master key.\n\n### Workarounds\n\nAvoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.\n\n### Resources\n\n- GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr\n- Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8","status":"published","published":"2026-02-25T19:00:07Z","modified":"2026-02-25T19:00:08Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high"}],"cwes":["CWE-1289"],"updated_at":"2026-11-02T14:39:27.949248Z"}],"nvd":[{"id":"CVE-2026-27610","description":"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.","status":"published","published":"2026-02-25T03:16:05.297Z","modified":"2026-06-26T16:59:57.737Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS: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","level":"high","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-1289"],"updated_at":"2026-11-02T14:12:07.027269Z"}],"osv":[{"id":"CVE-2026-27610","title":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","description":"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.","status":"published","published":"2026-02-25T02:19:56.022Z","modified":"2026-10-28T02:31:04.581903085Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high"}],"cwes":["CWE-1289"],"updated_at":"2026-11-02T15:45:00.180685Z"},{"id":"GHSA-jhp4-jvq3-w5xr","title":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","description":"### Impact\n\nThe `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.\n\n### Patches\n\nThe fix uses distinct cache keys for master key and read-only master key.\n\n### Workarounds\n\nAvoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.\n\n### Resources\n\n- GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr\n- Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8","status":"published","published":"2026-02-25T19:00:07Z","modified":"2026-02-25T19:41:37.189711Z","cvss":[{"version":"4.0","score":7,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","level":"high"}],"cwes":["CWE-1289"],"updated_at":"2026-11-02T15:46:50.336262Z"}]}}