CVE-2026-105647: Ghost: Server-Side Request Forgery in Bookmark Fetching
Impact
A validation issue allowed some functionality, such as Webmentions, to be abused by an unauthenticated user to make limited HTTP requests to hosts in the Ghost server's internal network. A successful attack would not result in any response data being returned.
Vulnerable versions
This vulnerability is present in Ghost from v6.54.1 up to v6.64.0.
Patches
v6.65.0 contains a fix for this issue.
How to update
For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.
If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.
References
Ghost thanks Nhat Anh Vu for disclosing this vulnerability responsibly.
For more information
If you have any questions or comments about this advisory, email us at security@ghost.org.
Other sources
Ghost is a Node.js content management system. From 6.54.1 until 6.65.0, a validation issue allowed some functionality, such as Webmentions, to be abused by an unauthenticated user to make limited HTTP requests to hosts in the Ghost server's internal network. A successful attack would not result in any response data being returned. This issue is fixed in version 6.65.0.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/ghostto a version that resolves this vulnerability.Fixed in 6.65.0 - Upgrade
Upgrade
Ghostto a version that resolves this vulnerability.Fixed in 6.65.0
Event History
Frequently Asked Questions
Which Ghost installations are affected?
Ghost versions from 6.54.1 through 6.65.0 are affected. The issue is fixed in version 6.65.0.
Does exploitation require an account or user interaction?
No. An unauthenticated attacker can abuse affected functionality, including Webmentions, without user interaction.
What can an attacker obtain through the SSRF?
The attacker can cause limited HTTP requests to hosts on the Ghost server's internal network. Response data is not returned to the attacker.
What should teams do if they cannot patch immediately?
The provided information does not specify a workaround. Prioritize upgrading to Ghost 6.65.0, especially where the Ghost server can reach sensitive internal services.