CVE-2026-29784

Ghost has incomplete CSRF protections around OTC use

Vulnerable versions

This vulnerability is present in Ghost from v5.101.6 up to v6.19.2.

How to update

For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.

If a project's Ghost is a Ghost-CLI install see the documentation on updating it to the latest version here.

For more information

If there are any questions or comments about this advisory, send an email to [email protected].

Incomplete CSRF protections around /session/verify made it possible to use OTCs in login sessions different from the requesting session. In some scenarios this might have made it easier for phishers to take over a Ghost site.

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.

CVE-2026-29784 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.19.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

v6.19.3 contains a fix for this issue.

1. What is CVE-2026-29784? CVE-2026-29784 is a high-severity cross-site request forgery (CSRF) vulnerability in ghost (npm), affecting versions >= 5.101.6, <= 6.19.2. It is fixed in 6.19.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2026-29784? CVE-2026-29784 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ghost are affected by CVE-2026-29784? ghost (npm) versions >= 5.101.6, <= 6.19.2 is affected.
4. Is there a fix for CVE-2026-29784? Yes. CVE-2026-29784 is fixed in 6.19.3. Upgrade to this version or later.
5. Is CVE-2026-29784 exploitable, and should I be worried? Whether CVE-2026-29784 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
6. What actually determines whether CVE-2026-29784 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.
7. How do I fix CVE-2026-29784? Upgrade ghost to 6.19.3 or later.

Other vulnerabilities in ghost