Quick answers
- Is CVE-2026-22597 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-22597 being exploited in the wild.
- How severe is CVE-2026-22597?
- Medium severity, with a CVSS score of 4, published 8 January 2026.
- Which products and versions are affected?
- ghost (npm) SEMVER:introduced=6.0.0,fixed=6.11.0.
- Is there a fix for CVE-2026-22597?
- Yes. ghost (npm): upgrade to 6.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-22597 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-22597?
- Check whether you run ghost (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ghost (npm): upgrade to 6.11.0 or later
npm install ghost@6.11.0
Technical details
This SSRF vulnerability exists in Ghost's media inliner mechanism and requires a valid authentication token for the Ghost Admin API, restricting exploitation to staff users. The vulnerability allows attackers to make arbitrary HTTP requests to internal systems by manipulating media inlining parameters, bypassing network-level access controls. Attack vector is network-based with low complexity and no user interaction required once authenticated. Patches are available in Ghost v5.130.6 and v6.11.0. The vulnerability affects versions 5.38.0–5.130.5 and 6.0.0–6.10.3.
Affected products
- Ghost Ghost 5.38.0 to 5.130.5, 6.0.0 to 6.10.3
Identifiers
- CVE-2026-22597
- GHSA-vmc4-9828-r48r
Timeline
- 2026-01-08: disclosed: Vulnerability published by Ghost security team
- 2026-01-08: patched: Patches released in versions 5.130.6 and 6.11.0