CVE-2026-27610

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-27610
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27610.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-27610
Aliases
Published
2026-02-25T02:19:56.022Z
Modified
2026-07-15T01:49:10.934564591Z
Severity
  • 7.0 (High) CVSS_V4 - 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 CVSS Calculator
Summary
Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
Details

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.

Database specific 
{
    "cwe_ids": [
        "CWE-1289"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27610.json",
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/parse-community/parse-dashboard

Affected ranges

Type
GIT
Repo
https://github.com/parse-community/parse-dashboard
Events
Introduced
e5cb66ccfcb4f192a18ca23d21f541bad2379aae
Fixed
9866a1b2392bfd3c37ee5b196327b45a1773bbee
Database specific 
{
    "extracted_events": [
        {
            "introduced": "7.3.0-alpha.42"
        },
        {
            "fixed": "9.0.0-alpha.8"
        }
    ],
    "source": "AFFECTED_FIELD"
}

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27610.json"