Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22597: CWE-918: Server-Side Request Forgery (SSRF) in TryGhost Ghost

0
Medium
VulnerabilityCVE-2026-22597cvecve-2026-22597cwe-918
Published: Sat Jan 10 2026 (01/10/2026, 02:57:36 UTC)
Source: CVE Database V5
Vendor/Project: TryGhost
Product: Ghost

Description

Ghost is a Node.js content management system. In versions 5.38.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost’s media inliner mechanism allows staff users in possession of a valid authentication token for the Ghost Admin API to exfiltrate data from internal systems via SSRF. This issue has been patched in versions 5.130.6 and 6.11.0.

AI-Powered Analysis

AILast updated: 01/17/2026, 07:58:36 UTC

Technical Analysis

CVE-2026-22597 is a Server-Side Request Forgery (SSRF) vulnerability identified in the TryGhost Ghost content management system, specifically within its media inliner feature. This vulnerability affects Ghost versions from 5.38.0 up to 5.130.5 and 6.0.0 up to 6.10.3. The media inliner mechanism, which processes media content for embedding or inlining, fails to properly validate or restrict URLs that staff users can request via the Ghost Admin API. As a result, an attacker with a valid authentication token and staff-level privileges can craft requests that cause the server to make arbitrary HTTP requests to internal or external systems. This can lead to unauthorized data exfiltration from internal services that are otherwise inaccessible externally, potentially exposing sensitive information such as internal APIs, databases, or metadata services. The vulnerability does not require user interaction beyond possessing a valid token, but it does require elevated privileges, limiting exploitation to trusted users or compromised accounts. The issue has been addressed in Ghost versions 5.130.6 and 6.11.0 by implementing stricter validation and restrictions on the URLs that the media inliner can access. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required beyond staff-level, no user interaction, and no impact on confidentiality, integrity, or availability beyond the SSRF scope, resulting in a medium severity score of 5.1. No public exploits or active exploitation campaigns have been reported to date.

Potential Impact

For European organizations using affected versions of the Ghost CMS, this SSRF vulnerability poses a risk of internal data exposure and reconnaissance. Attackers with staff-level access could leverage this flaw to access internal services that are not directly exposed to the internet, such as internal APIs, cloud metadata endpoints, or backend databases. This could lead to leakage of sensitive configuration data, credentials, or other internal information that could facilitate further attacks or lateral movement within the network. The impact is particularly significant for organizations hosting Ghost CMS on cloud infrastructure or within segmented internal networks where SSRF can bypass network controls. While the vulnerability does not directly allow remote code execution or denial of service, the ability to exfiltrate internal data can compromise confidentiality and aid attackers in escalating privileges or pivoting to more critical assets. Given the requirement for valid staff credentials, the threat is heightened if credential theft or insider threats are present. The medium severity rating reflects the moderate risk, but the potential for sensitive internal data exposure warrants prompt remediation.

Mitigation Recommendations

European organizations should immediately upgrade affected Ghost CMS instances to versions 5.130.6 or 6.11.0 or later, where the SSRF vulnerability has been patched. In addition to patching, organizations should implement strict access controls on the Ghost Admin API, ensuring that only trusted staff users have access and that authentication tokens are securely managed and rotated regularly. Network segmentation should be enforced to limit the Ghost server's ability to reach sensitive internal services, reducing the impact of potential SSRF exploitation. Monitoring and logging of API usage and unusual outbound requests from the Ghost server can help detect exploitation attempts. Employing web application firewalls (WAFs) with SSRF detection rules may provide additional protection. Finally, conduct regular security audits and penetration tests focusing on SSRF and API abuse scenarios to identify and remediate similar issues proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-07T21:50:39.532Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6961c40f19784dcf52acebdf

Added to database: 1/10/2026, 3:14:23 AM

Last enriched: 1/17/2026, 7:58:36 AM

Last updated: 2/4/2026, 10:28:39 PM

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats