Cyber Resilience

CVE-2026-27610

Parseplatform Parse Dashboard 7.3.0 … 9.0.0

Published
25 February 2026
Modified
26 June 2026
Patch / advisory
View advisory
CVSS Score v4 7.0
Click a component to see what it means
Raw vectorCVSS: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
EPSS Score 0.0034 27th percentile
Risk Priority 29 floored blend · peak EPSS

Summary

CVE-2026-27610 is a high-severity Improper Validation of Unsafe Equivalence in Input (CWE-1289) vulnerability in Parseplatform Parse Dashboard. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-1289

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-27609Same product: Parseplatform Parse Dashboard
CVE-2026-27595Same product: Parseplatform Parse Dashboard
CVE-2026-27608Same product: Parseplatform Parse Dashboard
CVE-2026-33539Same vendor: Parseplatform
CVE-2026-31856Same vendor: Parseplatform
CVE-2026-32248Same vendor: Parseplatform
CVE-2026-32234Same vendor: Parseplatform
CVE-2024-27298Same vendor: Parseplatform
CVE-2026-30941Same vendor: Parseplatform
CVE-2026-30848Same vendor: Parseplatform

Affected Assets

parseplatform
parse dashboard
7.3.0, 7.4.0, 7.5.0, 7.6.0, 8.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.2
  • V9.1.3
  • V10.4.6
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 requires validity checks on information inputs, directly stopping unsafe equivalence validation failures for identifiers and references.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and equivalence checking to prevent this class of flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect unsafe equivalence flaws but does not prevent them at design time.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate input validation rules that prevent unsafe equivalence checks.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include proper input validation and canonicalization to avoid unsafe equivalence.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require correct validation of resource identifiers and equivalence checks.

References