Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0amended

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

CVE-2026-27610GHSA-jhp4-jvq3-w5xr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (parse-dashboard 9.0.0-alpha.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm parse-dashboard

    Affected
    >= 7.3.0-alpha.42, < 9.0.0-alpha.8
    Fixed in
    9.0.0-alpha.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.0 · 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 · score source
EPSS
  • CVE-2026-27610: 0.38% estimated exploitation activity in the next 30 days; percentile 32.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jhp4-jvq3-w5xr

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-jhp4-jvq3-w5xr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27610

Advisory: Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
IDs: CVE-2026-27610, GHSA-jhp4-jvq3-w5xr
Record: https://patchnext.com/advisories/cve-2026-27610 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse-dashboard 9.0.0-alpha.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse-dashboard: affected >= 7.3.0-alpha.42, < 9.0.0-alpha.8; fixed in 9.0.0-alpha.8

## Suggested inspection (read-only)
- `npm ls parse-dashboard --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse-dashboard.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jhp4-jvq3-w5xr (OSV record GHSA-jhp4-jvq3-w5xr lists affected ranges: npm parse-dashboard >=7.3.0-alpha.42 <9.0.0-alpha.8 (fixed))
- Verified: https://github.com/advisories/GHSA-jhp4-jvq3-w5xr (GitHub-reviewed advisory GHSA-jhp4-jvq3-w5xr lists affected ranges: npm parse-dashboard >=7.3.0-alpha.42 <9.0.0-alpha.8)

Commands are suggestions: review each one before running it.

Loading voting…