CVE-2026-22597: 
JavaScript vulnerability analysis and mitigation

CVE-2026-22597 is a Server-Side Request Forgery (SSRF) vulnerability in Ghost's External Media Inliner mechanism, allowing authenticated staff users with a valid Ghost Admin API token to exfiltrate data from internal systems. It affects Ghost versions 5.38.0 through 5.130.5 and 6.0.0 through 6.10.3 (Node.js package). The vulnerability was discovered by Sho Odagiri of GMO Cybersecurity by Ierae, Inc. and disclosed on January 8, 2026. It carries a CVSS v3.1 base score of 2.7 (Low) and a CVSS v4.0 base score of 5.1 (Medium) (GitHub Advisory, Github Advisory).

The root cause is classified as CWE-918 (Server-Side Request Forgery). The ExternalMediaInliner component in Ghost used the generic @tryghost/request library to fetch external media URLs embedded in posts, without restricting requests to internal IP address ranges. A malicious staff user could craft media asset URLs pointing to internal network resources (e.g., http://169.254.169.254/ for cloud metadata or RFC 1918 addresses) and trigger the media inliner via the Ghost Admin API, causing the server to fetch and potentially expose the response content. The fix replaced the request library with the restricted request-external library, which performs DNS resolution checks and blocks requests resolving to private IP blocks (GitHub Advisory, Patch Commit).

Successful exploitation allows an authenticated staff-level attacker to make the Ghost server issue HTTP requests to internal systems and services that are otherwise inaccessible from the public internet, potentially exposing sensitive data such as cloud instance metadata, internal API responses, or other internal service data. There is no integrity or availability impact on the vulnerable system itself; the confidentiality impact is limited to subsequent/internal systems. The attack does not enable remote code execution or privilege escalation beyond data exfiltration from internal infrastructure (GitHub Advisory, Github Advisory).

No public proof-of-concept exploit code is known to exist, and there is no evidence of in-the-wild exploitation at this time. Exploitation requires a valid Ghost Admin API authentication token with at least staff-level privileges, significantly limiting the attacker pool. The EPSS score is approximately 0.033% (10th percentile), indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Github Advisory, Feedly).

1. Obtain Staff Credentials: Acquire a valid Ghost Admin API authentication token for a staff-level or higher account on a vulnerable Ghost instance (versions 5.38.0–5.130.5 or 6.0.0–6.10.3).
2. Identify Target Internal Resource: Determine the internal URL to probe, such as the cloud metadata endpoint (http://169.254.169.254/latest/meta-data/) or an internal service (e.g., http://192.168.1.1/admin).
3. Craft Malicious Post Content: Create or edit a Ghost post via the Admin API, embedding the target internal URL as a media asset reference (e.g., an image src pointing to the internal URL).
4. Trigger the Media Inliner: Use the Ghost Admin API to invoke the External Media Inliner feature on the crafted post, causing the Ghost server to fetch the embedded URL.
5. Exfiltrate Response Data: Observe the server's behavior or any error responses/logs that may reflect the content retrieved from the internal URL, thereby exfiltrating data from the internal system (GitHub Advisory, Patch Commit).

• Network: Outbound HTTP requests from the Ghost server process to internal IP ranges (RFC 1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or link-local addresses (169.254.0.0/16); unexpected requests to cloud metadata endpoints (e.g., 169.254.169.254).
• Logs: Ghost application logs showing ExternalMediaInliner fetch attempts to internal or non-public URLs; error log entries such as Error downloading remote media: http://<internal-ip>/....
• API Activity: Ghost Admin API logs showing unusual invocations of the media inliner feature, particularly by staff accounts, with post content containing non-standard or internal URLs as media sources.
• Process: Unusual outbound network connections originating from the Node.js Ghost process to internal network segments not typically accessed by the CMS (Patch Commit, GitHub Advisory).

Upgrade Ghost to version 5.130.6 (for the 5.x branch) or 6.11.0 (for the 6.x branch) or later, which replace the vulnerable @tryghost/request library in ExternalMediaInliner with the restricted request-external library that blocks requests resolving to internal IP addresses. As an interim measure, implement network-level controls to prevent the Ghost server from making outbound requests to internal IP ranges and cloud metadata endpoints. Additionally, audit Ghost Admin API token usage, revoke any unnecessary or suspicious credentials, and monitor API activity for anomalous media inliner invocations (GitHub Advisory, Patch Commit).

The vulnerability was responsibly disclosed by Sho Odagiri of GMO Cybersecurity by Ierae, Inc. and acknowledged by the Ghost team in their official security advisory. The Ghost maintainer kevinansfield published the advisory on January 8, 2026. Community discussion was limited, with some social media mentions on Bluesky shortly after disclosure, reflecting routine awareness rather than significant concern given the high privilege requirement for exploitation (GitHub Advisory).