EUVD-2026-39024
GHSA-ch52-px8q-f22j
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
DNS rebinding requires no auth but demands DNS control and timing precision (AC:H); SSRF-class internal access implies at least low confidentiality impact (C:L) from probing internal service responses.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Ghost is a Node.js content management system. From 6.0.9 until 6.21.1, Ghost’s private-IP check for outbound HTTP requests could be bypassed via DNS rebinding, allowing an attacker to coerce the Ghost server into reaching hosts on internal networks through features that issue external fetches. This vulnerability is fixed in 6.21.1.
AnalysisAI
DNS rebinding bypasses Ghost CMS's private-IP validation for outbound HTTP requests, enabling server-side request forgery (SSRF) against internal network resources. Versions 6.0.9 through 6.21.0 are affected; the root cause is a TOCTOU race (CWE-367) between Ghost's allowlist check and the actual TCP connection, which a DNS-rebinding attacker exploits by switching DNS records between check-time and connect-time. No public exploit code identified and not listed in CISA KEV, but the scope-changed CVSS rating (S:C) reflects that successful exploitation escapes Ghost's network boundary into adjacent internal infrastructure.
Technical ContextAI
Ghost is an open-source Node.js content management system (CPE: cpe:2.3:a:tryghost:ghost) that exposes features - webhooks, RSS imports, link unfurling, custom integrations - which issue outbound HTTP fetches. To prevent SSRF, Ghost validates that the resolved IP of a requested hostname is not within RFC-1918 private ranges before connecting. The flaw (CWE-367: Time-of-Check Time-of-Use) arises because DNS resolution at check-time is distinct from the resolution the HTTP client uses at connect-time. An attacker who controls a DNS server can serve a public IP during Ghost's check phase, then switch the DNS record to a private/internal IP - with a very short TTL - before Ghost's HTTP client establishes the TCP connection. This classic DNS rebinding pattern defeats point-in-time IP validation without requiring any change to Ghost's own configuration.
RemediationAI
Upgrade to Ghost 6.21.1 or later, which contains the vendor-released fix per advisory GHSA-ch52-px8q-f22j at https://github.com/TryGhost/Ghost/security/advisories/GHSA-ch52-px8q-f22j. If immediate upgrade is not feasible, apply egress firewall rules at the network or container level that block Ghost's process from initiating TCP connections to RFC-1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local ranges (169.254.0.0/16), and other internal CIDRs; this network-layer control prevents the rebinded connection from succeeding even when the application-level check is bypassed, though misconfiguration may disrupt legitimate outbound Ghost features. As a more aggressive workaround, disabling Ghost features that perform external HTTP fetches - webhooks, custom integrations, RSS imports - eliminates the attack surface at the cost of losing that functionality entirely.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today