Summary
Parse Dashboard is Missing CSRF Protection for its Agent Endpoint
Workarounds
Remove the agent configuration block from your dashboard configuration. Dashboards without an agent config are not affected.
Resources
Impact
The AI Agent API endpoint (POST /apps/:appId/agent) lacks CSRF protection. An attacker can craft a malicious page that, when visited by an authenticated dashboard user, submits requests to the agent endpoint using the victim's session.
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The fix adds CSRF middleware to the agent endpoint and embeds a CSRF token in the dashboard page.
Frequently Asked Questions
- What is CVE-2026-27609? CVE-2026-27609 is a high-severity cross-site request forgery (CSRF) vulnerability in parse-dashboard (npm), affecting versions >= 7.3.0-alpha.42, < 9.0.0-alpha.8. It is fixed in 9.0.0-alpha.8. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of parse-dashboard are affected by CVE-2026-27609? parse-dashboard (npm) versions >= 7.3.0-alpha.42, < 9.0.0-alpha.8 is affected.
- Is there a fix for CVE-2026-27609? Yes. CVE-2026-27609 is fixed in 9.0.0-alpha.8. Upgrade to this version or later.
- Is CVE-2026-27609 exploitable, and should I be worried? Whether CVE-2026-27609 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27609 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27609? Upgrade
parse-dashboardto 9.0.0-alpha.8 or later.