Quick answers
- Is CVE-2026-105647 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105647 being exploited in the wild.
- How severe is CVE-2026-105647?
- Medium severity, with a CVSS score of 4, published 5 October 2026.
- Which products and versions are affected?
- Ghost 6.54.1 to 6.65.0; ghost (npm) >= 6.54.1, < 6.65.0, SEMVER:introduced=6.54.1,fixed=6.65.0.
- Is there a fix for CVE-2026-105647?
- Yes. ghost (npm): upgrade to 6.65.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105647 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105647?
- Check whether you run Ghost or ghost (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ghost (npm): upgrade to 6.65.0 or later
npm install ghost@6.65.0
Technical details
A validation issue in Ghost's external request handling, particularly in favicon lookup and oEmbed functionality, fails to properly restrict destination URLs. Unauthenticated users can exploit Webmentions and similar features to make arbitrary HTTP requests to the Ghost server's internal network (SSRF). The fix adds a fetchFirstChunk() method that limits request handling and validates URLs appropriately; the attack requires no special authentication or user interaction.
Affected products
- Ghost Ghost 6.54.1 to 6.65.0
Identifiers
- CVE-2026-105647
- GHSA-322m-ff4g-9vx9
Timeline
- 2026-10-05: disclosed
- 2026-09-21: patched