Security readout for executives and security teams
Plain-English summary
Parse Dashboard can accidentally give a read-only session the full master key under specific timing conditions. That key can allow high-impact changes to Parse Server data or configuration. The issue affects alpha versions 7.3.0-alpha.42 through before 9.0.0-alpha.8 and is fixed in 9.0.0-alpha.8.
Executive priority
Prioritize if Parse Dashboard manages production Parse Server applications or sensitive data. The issue can expose a full master key to a lower-privileged user, creating material integrity risk. If only non-production alpha deployments are affected, handle through normal urgent patching.
Technical view
ConfigKeyCache reuses the same cache key for function-typed masterKey and readOnlyMasterKey resolution. Cache collision can return the full master key to read-only users, or the read-only key to regular users. CVSS 4.0 is 7.0 with network access, low privileges, high attack complexity, and high integrity impact.
Likely exposure
Exposure is likely limited to deployments running affected Parse Dashboard alpha versions with function-typed master keys. The advisory also names removing the agent configuration block as a workaround, suggesting that configuration can be relevant. Confirm exact version and dashboard configuration.
Exploitation context
The source describes exploitation as requiring a read-only or regular authenticated user and specific timing conditions. CISA KEV is false in the provided data, and no cited source reports active exploitation. Do not treat this as proven exploited in the wild.
Researcher notes
Evidence comes from the GitHub advisory, CVE record, release, and fixing commit. The fix uses distinct cache keys for masterKey and readOnlyMasterKey. Public sources do not provide evidence of active exploitation or broader affected products beyond parse-community parse-dashboard.
Mitigation direction
- Upgrade Parse Dashboard to 9.0.0-alpha.8 or later.
- Avoid using function-typed master keys until upgraded.
- Remove the agent configuration block if using the vendor workaround.
- Review vendor advisory before applying configuration changes.
Validation and detection
- Identify Parse Dashboard versions in all environments.
- Check whether versions are >=7.3.0-alpha.42 and <9.0.0-alpha.8.
- Review dashboard configuration for function-typed master keys.
- Check whether an agent configuration block is present.
- After upgrade, confirm version 9.0.0-alpha.8 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1289: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27610 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
7HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xrCVE reference · x_refsource_CONFIRM
- https://github.com/parse-community/parse-dashboard/commit/f92a9ef5246d57e51696bd881a15f3b133b2bb50CVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Unsafe Equivalence in Input
Improper Validation of Unsafe Equivalence in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.