Skip to main content
VulnerabilityPublished

CVE-2026-105676: TryGhost Ghost · Path Traversal

Affects TryGhost GhostSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.9 Medium : upgrade to 6.64.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.64.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade TryGhost Ghost to 6.64.0.

Affected software

ProductAffectedFixed in
TryGhostGhostAffected
  • >=1.20.0 <6.64.0
Fixed in
  • 6.64.0

AI-suggested

Upgrade Ghost to version 6.64.0 or later, where this vulnerability is fixed. For self-hosters using Docker, update using the official Ghost Docker image and follow the documented update procedures. For Ghost-CLI installations, update to the latest version as per official documentation. No other mitigation is required as the fix is available.

Description

CVE-2026-105676 is a path traversal vulnerability in TryGhost Ghost affecting versions from 1.20.0 up to but not including 6.64.0. It allows an authenticated Administrator to read JSON files outside the active theme's directory, potentially exposing sensitive server configuration secrets. The issue is fixed in version 6.64.0.

References

Community reviews

Loading reviews…