Skip to main content
VulnerabilityPublished

CVE-2026-53943: TryGhost Ghost · Use of Cache Containing Sensitive Information

Affects TryGhost GhostSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 6.37.0 as a priority.

Data as of 6 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 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 6 Nov 2026.

What to do

Upgrade Ghost and ghost to 6.37.0.

Affected software

ProductAffectedFixed in
TryGhostGhostAffected
  • >=4.0.0 <6.37.0
Fixed in
  • 6.37.0
npmghostpkg:npm/ghostOther threatsAffected
  • <6.37.0
Fixed in
  • 6.37.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Ghost to version 6.37.0 or later, where this vulnerability is fixed. Until then, avoid deploying Ghost behind shared caching layers that share cached content between different visitors, or separate the frontend and admin panel domains to reduce risk. Patch status is confirmed fixed in 6.37.0.

Description

Ghost is a Node.js content management system. From until 6.37.0, when Ghost is behind a shared caching layer that results in cached content being shared between different visitors, an unauthenticated user could send an x-ghost-preview header that altered the rendered frontend response. In affected cache configurations, that response could be stored and served to subsequent visitors requesting the same page, allowing cache poisoning of request-specific preview output. When running Ghost's frontend and admin panel on the same domain this could be used to take over staff user accounts. When running these on different domains staff accounts have no exposure. This vulnerability is fixed in 6.37.0.

References

Community reviews

Loading reviews…