CVE-2026-27610: parse-dashboard · Improper Validation of Unsafe Equivalence in Input
Affects parse-dashboardSource CVE Database V5
Not known to be exploited · CVSS 7.0 High : upgrade to 9.0.0-alpha.8 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.0.0-alpha.8
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade parse-dashboard to 9.0.0-alpha.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-dashboard | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-27610, organizations should upgrade parse-dashboard to version 9.0.0-alpha.8 or later, where the issue is fixed by using distinct cache keys for master and read-only master keys. If immediate upgrade is not feasible, apply the following workarounds: avoid using function-typed master keys in the configuration, as these trigger the vulnerable cache key handling; alternatively, remove the agent configuration block from the dashboard configuration to prevent the caching issue. Additionally, restrict dashboard access to trusted users and networks to reduce exposure. Implement monitoring and alerting for unusual access patterns or privilege escalations within parse-dashboard. Conduct thorough audits of user permissions and keys to detect any unauthorized access. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential compromises.
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.
References
- github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr (opens in a new tab)
- github.com/parse-community/parse-dashboard/commit/f92a9ef5246d57e51696bd881a15f3b133b2bb50 (opens in a new tab)
- github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8 (opens in a new tab)