GHSA-JHP4-JVQ3-W5XR
Vulnerability from github – Published: 2026-02-25 19:00 – Updated: 2026-02-25 19:00
VLAI?
Summary
Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
Details
Impact
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.
Patches
The fix uses distinct cache keys for master key and read-only master key.
Workarounds
Avoid using function-typed master keys, or remove the agent configuration block from your dashboard configuration.
Resources
- GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr
- Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8
Severity ?
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "parse-dashboard"
},
"ranges": [
{
"events": [
{
"introduced": "7.3.0-alpha.42"
},
{
"fixed": "9.0.0-alpha.8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-27610"
],
"database_specific": {
"cwe_ids": [
"CWE-1289"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-25T19:00:07Z",
"nvd_published_at": "2026-02-25T03:16:05Z",
"severity": "HIGH"
},
"details": "### Impact\n\nThe `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.\n\n### Patches\n\nThe fix uses distinct cache keys for master key and read-only master key.\n\n### Workarounds\n\nAvoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.\n\n### Resources\n\n- GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr\n- Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8",
"id": "GHSA-jhp4-jvq3-w5xr",
"modified": "2026-02-25T19:00:07Z",
"published": "2026-02-25T19:00:07Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27610"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-dashboard/commit/f92a9ef5246d57e51696bd881a15f3b133b2bb50"
},
{
"type": "PACKAGE",
"url": "https://github.com/parse-community/parse-dashboard"
},
{
"type": "WEB",
"url": "https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8"
}
],
"schema_version": "1.4.0",
"severity": [
{
"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",
"type": "CVSS_V4"
}
],
"summary": "Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…