CVE-2026-27610

Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions

MEDIUM
5.3
CVSS Score
Published: February 25, 2026 at 02:19 AM UTC
Updated: June 27, 2026 at 11:41 AM UTC
2 products affected across 2 vendorsParse DashboardParse Dashboard

Using parse-dashboard by parse-community?

Get instant alerts when new vulnerabilities affect parse-dashboard - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

7.3.0 alpha427.3.0 alpha437.3.0 alpha447.3.0 alpha57.3.0 alpha67.3.0 alpha77.3.0 alpha87.3.0 alpha97.4.0 alpha17.4.0 alpha27.4.0 alpha37.4.0 alpha47.4.0 alpha57.5.0 alpha17.5.0 alpha27.6.0 alpha17.6.0 alpha107.6.0 alpha117.6.0 alpha127.6.0 alpha137.6.0 alpha27.6.0 alpha37.6.0 alpha47.6.0 alpha57.6.0 alpha67.6.0 alpha77.6.0 alpha87.6.0 alpha98.0.0 alpha18.0.0 alpha28.0.0 alpha38.0.0 alpha48.0.0 alpha58.0.0 alpha68.1.0 alpha18.1.0 alpha108.1.0 alpha118.1.0 alpha128.1.0 alpha138.1.0 alpha28.1.0 alpha38.1.0 alpha48.1.0 alpha58.1.0 alpha68.1.0 alpha78.1.0 alpha88.1.0 alpha98.1.1 alpha18.2.0 alpha18.2.0 alpha108.2.0 alpha118.2.0 alpha128.2.0 alpha138.2.0 alpha148.2.0 alpha158.2.0 alpha168.2.0 alpha178.2.0 alpha188.2.0 alpha198.2.0 alpha28.2.0 alpha208.2.0 alpha218.2.0 alpha228.2.0 alpha238.2.0 alpha248.2.0 alpha258.2.0 alpha268.2.0 alpha278.2.0 alpha38.2.0 alpha48.2.0 alpha58.2.0 alpha68.2.0 alpha78.2.0 alpha88.2.0 alpha98.3.0 alpha18.3.0 alpha108.3.0 alpha118.3.0 alpha128.3.0 alpha138.3.0 alpha148.3.0 alpha158.3.0 alpha168.3.0 alpha178.3.0 alpha188.3.0 alpha198.3.0 alpha28.3.0 alpha208.3.0 alpha218.3.0 alpha228.3.0 alpha238.3.0 alpha248.3.0 alpha258.3.0 alpha268.3.0 alpha278.3.0 alpha288.3.0 alpha298.3.0 alpha38.3.0 alpha308.3.0 alpha318.3.0 alpha328.3.0 alpha338.3.0 alpha348.3.0 alpha358.3.0 alpha368.3.0 alpha378.3.0 alpha388.3.0 alpha398.3.0 alpha48.3.0 alpha408.3.0 alpha418.3.0 alpha428.3.0 alpha438.3.0 alpha58.3.0 alpha68.3.0 alpha78.3.0 alpha88.3.0 alpha98.4.0 alpha18.4.1 alpha18.4.1 alpha28.5.0 alpha18.5.0 alpha28.5.0 alpha38.5.0 alpha48.5.0 alpha58.5.0 alpha68.5.0 alpha79.0.0 alpha19.0.0 alpha29.0.0 alpha39.0.0 alpha49.0.0 alpha59.0.0 alpha69.0.0 alpha7
v < 9.0.0-alpha.8
Affected range stops below 9.0.0-alpha.8, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-1289

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card