Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

Parse Dashboard is Missing Authorization for its Agent Endpoint

CVE-2026-27608GHSA-cvwj-6c9h-jg6v

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.7
    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
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N · score source
EPSS
  • CVE-2026-27608: 0.26% estimated exploitation activity in the next 30 days; percentile 17.58 (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 AI Agent API endpoint (POST /apps/:appId/agent) does not enforce authorization. Authenticated users scoped to specific apps can access any other app's agent endpoint by changing the app ID in the URL. Read-only users are given the full master key instead of the read-only master key and can supply write permissions in the request body to perform write and delete operations. Affected are only dashboards with agent configuration enabled. Patches The fix adds per-app authorization checks and restricts read-only users to the readOnlyMasterKey with write permissions stripped server-side. Workarounds Remove the agent configuration block from your dashboard configuration. Dashboards without an agent config are not affected. Resources - GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-cvwj-6c9h-jg6v - 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 4 · amended ·

    Amended from ghsa record GHSA-cvwj-6c9h-jg6v

  2. Revision 3 · amended ·

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

  3. Revision 2 · amended ·

    Amended from osv record GHSA-cvwj-6c9h-jg6v

  4. Revision 1 · created ·

    Published from ghsa record GHSA-cvwj-6c9h-jg6v

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-27608

Advisory: Parse Dashboard is Missing Authorization for its Agent Endpoint
IDs: CVE-2026-27608, GHSA-cvwj-6c9h-jg6v
Record: https://patchnext.com/advisories/cve-2026-27608 (revision 4, 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: Critical (CVSS 9.3)
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.7; 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://github.com/advisories/GHSA-cvwj-6c9h-jg6v (GitHub-reviewed advisory GHSA-cvwj-6c9h-jg6v lists affected ranges: npm parse-dashboard >=7.3.0-alpha.42 <=9.0.0-alpha.7)
- Verified: https://osv.dev/vulnerability/GHSA-cvwj-6c9h-jg6v (OSV record GHSA-cvwj-6c9h-jg6v lists affected ranges: npm parse-dashboard >=7.3.0-alpha.42 <9.0.0-alpha.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…