Parse Dashboard is Missing Authorization for its Agent Endpoint

高 8.1CVE-2026-27608 · GHSA-cvwj-6c9h-jg6v · 25/02/2026 公開 · 26/06/2026 更新

要点

CVE-2026-27608 は parse dashboard (parseplatform), parse-dashboard に影響する深刻度「高」 (CVSS 8.1) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.26%（全脆弱性の 17.6% より高い）。
対処：9.0.0-alpha.8 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
parse dashboard parseplatform	`= 7.3.0= 7.4.0= 7.5.0= 7.6.0= 8.0.0= 8.1.0= 8.1.1= 8.2.0= 8.3.0= 8.4.0= 8.4.1= 8.5.0= 9.0.0`	修正版なし
parse-dashboard npm	`≥ 7.3.0-alpha.42, < 9.0.0-alpha.8`	`9.0.0-alpha.8`

概要

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

NVD の説明

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.