Ghost Vulnerable to Remote Code Execution via Malicious Themes

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-29053: 4.90% estimated exploitation activity in the next 30 days; percentile 92.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Specifically crafted malicious themes can execute arbitrary code on the server running Ghost. Vulnerable Versions This vulnerability is present in Ghost v0.7.2 to v6.19.0. Patches v6.19.1 contains a fix for this issue. Workarounds Ghost generally recommends users refrain from installing untrusted themes. If a malicious theme has already been installed, it is recommended to uninstall the theme and then inspect it to understand its impact, which will be attack-specific. References Ghost thanks Cristian-Alexandru Staicu at Endor Labs for disclosing this vulnerability responsibly. For more information If there are any questions or comments about this advisory, email Ghost at security@ghost.org.

Published by the source

3 Mar 2026, 20:01 UTC

Last modified by the source

7 Mar 2026, 09:41 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cgc2-rcrh-qr5x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cgc2-rcrh-qr5x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-29053

Advisory: Ghost Vulnerable to Remote Code Execution via Malicious Themes
IDs: CVE-2026-29053, GHSA-cgc2-rcrh-qr5x
Record: https://patchnext.com/advisories/cve-2026-29053 (revision 2, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ghost 6.19.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ghost: affected >= 0.7.2, <= 6.19.0; fixed in 6.19.1

## Suggested inspection (read-only)
- `npm ls ghost --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ghost.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cgc2-rcrh-qr5x (OSV record GHSA-cgc2-rcrh-qr5x lists affected ranges: npm ghost >=0.7.2 <6.19.1 (fixed))
- Verified: https://github.com/advisories/GHSA-cgc2-rcrh-qr5x (GitHub-reviewed advisory GHSA-cgc2-rcrh-qr5x lists affected ranges: npm ghost >=0.7.2 <=6.19.0)

Commands are suggestions: review each one before running it.