Which versions of Parse Dashboard are affected by CVE-2026-27608?

Parse Dashboard versions 7.3.0-alpha through 9.0.0-alpha.7 contain an authorization flaw in the AI Agent feature that allows authenticated users with limited permissions to gain unrestricted…. A patch is available.

How to fix or mitigate CVE-2026-27608?

Within 24 hours: identify all Parse Dashboard instances in your environment and verify their current versions against the vulnerable range (7.3.0-alpha.42 through 9.0.0-alpha.7); within 7 days: upgrade all affected instances to the patched version specified in the vendor security advisory; within 30 days: audit POST /apps/:appId/agent endpoint logs for suspicious cross-application access requests and confirm all instances are running patched versions.

Parse Dashboard CVE-2026-27608

Q: What is the CVSS score of CVE-2026-27608?

CVE-2026-27608 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: 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/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 exploitation probability: 0.0%.

CRITICAL

Missing Authorization (CWE-862)

2026-02-25 security-advisories@github.com

GHSA-cvwj-6c9h-jg6v

Authentication Bypass Parse Dashboard

9.3

CVSS 4.0 · Vendor: github

Severity by source

Vendor (github) PRIMARY

9.3 CRITICAL

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

vuln.today AI

9.6 CRITICAL

Network-reachable endpoint exploitable by any low-privileged authenticated user (PR:L, AC:L); scope changes as the dashboard boundary is crossed into other apps/backend (S:C); high confidentiality and integrity, no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Updated

Jun 26, 2026 - 17:13 vuln.today

v3 (cvss_changed)

Source Code Evidence Fetched

Jun 26, 2026 - 17:12 vuln.today

Analysis Updated

Jun 26, 2026 - 17:12 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 26, 2026 - 17:07 vuln.today

cvss_changed

Severity Changed

Jun 26, 2026 - 17:07 NVD

HIGH CRITICAL

CVSS changed

Jun 26, 2026 - 17:07 NVD

8.1 (HIGH) 9.3 (CRITICAL)

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Feb 25, 2026 - 03:16 nvd

HIGH 8.1

DescriptionCVE.org

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 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. Only dashboards with agent configuration enabled are affected. The fix in version 9.0.0-alpha.8 adds per-app authorization checks and restricts read-only users to the readOnlyMasterKey with write permissions stripped server-side. As a workaround, remove the agent configuration block from your dashboard configuration. Dashboards without an agent config are not affected.

AnalysisAI

Broken authorization in Parse Dashboard's AI Agent endpoint (POST /apps/:appId/agent) lets any authenticated user reach apps they are not scoped to and lets read-only users escalate to full read-write control. Present in versions 7.3.0-alpha.42 through 9.0.0-alpha.7, the endpoint omits per-app authorization checks and hands read-only users the full master key, so an attacker can swap the app ID in the URL to act against other tenants and supply write permissions to perform write/delete operations. No public exploit is identified at time of analysis, and the EPSS probability is very low (0.03%), but it is trivially exploitable by any logged-in low-privilege user where the agent feature is enabled.

Technical ContextAI

Parse Dashboard is the Node.js web management UI for Parse Server, an open-source Backend-as-a-Service platform; the dashboard mediates privileged access to Parse Server apps using master keys and per-app user scoping. This is a CWE-862 Missing Authorization flaw: the AI Agent route trusts the app ID supplied in the request path without verifying the caller is actually authorized for that app, and it provisions the agent with the full master key regardless of the user's read-only role. The CPE data confirms the affected component is parseplatform:parse_dashboard on the node.js platform, and the vulnerable range covers a span of alpha pre-releases (7.3.0-alpha.42 onward, plus 7.4.0 alphas) up to 9.0.0-alpha.7. The fix in 9.0.0-alpha.8 introduces per-app authorization enforcement and downgrades read-only users to the readOnlyMasterKey with write permissions stripped server-side.

RemediationAI

Vendor-released patch: upgrade to Parse Dashboard 9.0.0-alpha.8, which adds per-app authorization checks and restricts read-only users to the readOnlyMasterKey with write permissions stripped server-side (release: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8). If you cannot upgrade immediately, the vendor-supported workaround is to remove the agent configuration block from your dashboard configuration entirely; dashboards without an agent config are not affected, with the trade-off being complete loss of the AI Agent feature until you patch. As an additional interim control, restrict dashboard accounts and tighten per-app user scoping, and avoid relying on read-only roles as a security boundary while the flaw is present, since read-only users can currently escalate to write/delete. Refer to advisory GHSA-cvwj-6c9h-jg6v for authoritative guidance.