# CVE-2026-29053: Ghost Vulnerable to Remote Code Execution via Malicious Themes

> Attackers can execute arbitrary code on Ghost servers by uploading malicious themes, requiring an upgrade to the latest version.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** BIT-ghost-2026-29053, GHSA-cgc2-rcrh-qr5x

## What is CVE-2026-29053?

CVE-2026-29053 is a high-severity code injection vulnerability in TryGhost Ghost, published on 5 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Ghost is a Node.js content management system. From version 0.7.2 to 6.19.0, specifically crafted malicious themes can execute arbitrary code on the server running Ghost. This issue has been patched in version 6.19.1.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-29053?

3 open source packages ship an affected version, including ghost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 0.7.2 | 6.19.1 |
| `ghost` | npm | From 0.7.2 | 6.19.1 |
| `ghost` | npm | From 0.7.2 | 6.19.1 |

Products: Ghost Ghost.

## How do I fix CVE-2026-29053?

Upgrade ghost to 6.19.1 or later.

## Is CVE-2026-29053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29053 exists.

Public exploit code:

- https://github.com/rootxran/CVE-2026-29053 (github_poc): https://github.com/rootxran/CVE-2026-29053
- (RCE) vulnerability discovered in Ghost CMS (specifically affecting versions 0.7.2 through 6.19.0) (github_poc): https://github.com/AC8999/CVE-2026-29053
- Ghost CMS Remote Code Execution (metasploit)
- Ghost_CMS 6.19.0  - Remote Code Execution (exploitdb)

## Other vulnerabilities in TryGhost Ghost

- [CVE-2022-27139](https://insights.sbomify.com/CVE-2022-27139/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-28397](https://insights.sbomify.com/CVE-2022-28397/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-41654](https://insights.sbomify.com/CVE-2022-41654/): ghost vulnerable to unauthorized newsletter modification via improper access controls (critical 9.6)
- [CVE-2026-26980](https://insights.sbomify.com/CVE-2026-26980/): Ghost has a SQL Injection in its Content API (critical 9.4)
- [CVE-2024-34451](https://insights.sbomify.com/CVE-2024-34451/): Security feature bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29053 and fix it if it is affected.

What it is: CVE-2026-29053 is a high-severity code injection vulnerability in TryGhost Ghost, published on 5 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29053 exists.

Affected packages and fixed versions:
- ghost (Bitnami): affected from 0.7.2; fixed in 6.19.1
- ghost (npm): affected from 0.7.2; fixed in 6.19.1
- ghost (npm): affected from 0.7.2; fixed in 6.19.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29053/ (Markdown: https://insights.sbomify.com/CVE-2026-29053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29053
- OSV: https://osv.dev/vulnerability/CVE-2026-29053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29053/
Summaries are generated and may contain mistakes; the official description above is the record.