CVE-2026-53945: Ghost CMS SSRF Vulnerability

CVE-2026-53945 Overview

CVE-2026-53945 is a Server-Side Request Forgery (SSRF) vulnerability in Ghost, a Node.js content management system. Ghost's private-IP check for outbound HTTP requests can be bypassed using DNS rebinding. Attackers can coerce the Ghost server into reaching hosts on internal networks through features that issue external fetches. The flaw affects Ghost versions 6.0.9 through 6.21.0 and is fixed in 6.21.1. The root weakness is classified as [CWE-367] Time-of-Check Time-of-Use (TOCTOU), where the IP address validated during the initial DNS lookup differs from the IP used during the actual connection.

Critical Impact
Authenticated or unauthenticated attackers can bypass private-IP filtering to reach internal network resources via outbound HTTP fetch features in Ghost.

Affected Products

Ghost (Node.js CMS) versions 6.0.9 through 6.21.0
Ghost self-hosted deployments using vulnerable outbound fetch features
Ghost(Pro) instances prior to the 6.21.1 patch

Discovery Timeline

2026-06-24 - CVE CVE-2026-53945 published to NVD
2026-06-24 - Last updated in NVD database

Technical Details for CVE-2026-53945

Vulnerability Analysis

Ghost performs outbound HTTP requests for features such as webhook delivery, oEmbed previews, and external resource fetching. To prevent SSRF, Ghost resolves the destination hostname and validates the resulting IP address against a private-network blocklist. The validation logic suffers from a race condition between resolution and connection. An attacker controlling a DNS server can return a public IP on the first lookup, satisfying the validation check, then return a private IP such as 127.0.0.1 or 169.254.169.254 on the second lookup used by the HTTP client. This DNS rebinding technique allows requests to reach internal services, including cloud metadata endpoints, internal admin panels, and unauthenticated services on the local network.

Root Cause

The vulnerability stems from a Time-of-Check Time-of-Use (TOCTOU) flaw in Ghost's SSRF protection. The IP validation occurs during a separate DNS resolution from the one performed by the underlying HTTP client. Because Ghost does not pin the resolved address between the check and the actual request, an attacker-controlled DNS response can swap the address between operations.

Attack Vector

An attacker registers a domain with a short Time-To-Live (TTL) and configures authoritative DNS to alternate responses. The attacker then submits the malicious hostname to a Ghost feature that performs outbound fetches. Ghost resolves the hostname, sees a public IP, and proceeds. The HTTP client re-resolves the hostname and receives an internal IP, connecting to the internal target. No exploit code is required beyond a controlled DNS server and a URL submission to a vulnerable endpoint. See the GitHub Security Advisory for technical details.

Detection Methods for CVE-2026-53945

Indicators of Compromise

Outbound HTTP requests from the Ghost server to RFC1918 addresses, loopback ranges, or cloud metadata endpoints such as 169.254.169.254
DNS queries from the Ghost host returning rapidly alternating A records for the same hostname
Unexpected webhook, oEmbed, or external resource fetches submitted to Ghost admin or API endpoints referencing attacker-controlled domains

Detection Strategies

Inspect Ghost application logs for outbound fetch operations targeting suspicious hostnames followed by connections to internal IP ranges
Correlate DNS resolver telemetry with HTTP egress logs to identify hostnames returning both public and private IP answers within short windows
Alert on Ghost server processes initiating connections to link-local addresses or internal management interfaces

Monitoring Recommendations

Forward Ghost access logs, DNS query logs, and egress firewall logs to a centralized analytics platform for correlation
Monitor for HTTP 200 responses from internal IPs originating from the Ghost worker process
Track Ghost version strings across infrastructure to identify hosts still running versions earlier than 6.21.1

How to Mitigate CVE-2026-53945

Immediate Actions Required

Upgrade Ghost to version 6.21.1 or later on all self-hosted instances
Restrict outbound network access from the Ghost server to only required destinations using egress firewall rules
Block the Ghost host from reaching cloud metadata endpoints such as 169.254.169.254 unless explicitly required

Patch Information

Ghost version 6.21.1 resolves the DNS rebinding bypass. The fix is published in the Ghost GitHub Security Advisory GHSA-ch52-px8q-f22j. Operators of Ghost(Pro) receive the patch automatically. Self-hosted administrators must upgrade through standard Ghost CLI procedures.

Workarounds

Deploy an egress proxy that enforces hostname-to-IP allowlisting and pins resolved addresses for the lifetime of each request
Use network segmentation to isolate the Ghost server from internal management networks and cloud metadata services
Disable Ghost features that perform arbitrary outbound fetches, such as oEmbed previews, until the upgrade is applied

bash

# Example egress firewall rule blocking cloud metadata access from the Ghost host
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 127.0.0.0/8 ! -o lo -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -j DROP
iptables -A OUTPUT -d 172.16.0.0/12 -j DROP
iptables -A OUTPUT -d 192.168.0.0/16 -j DROP