Skip to content

GHSA-wvp2-4qqp-4h3r BIT-ghost-2026-53944 CVE-2026-53944

Ghost: Private IP filtering bypass to make server-side requests to internal services

Medium npm
Severity
5.8 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.33%
Chance of exploitation in the next 30 days. Higher than 26.02% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-184 Incomplete List of Disallowed Inputs
CWE-918 Server-Side Request Forgery (SSRF)
Fix
6.21.1
Upgrade ghost to this version or later

Description

Impact

When making an external request, it is possible to bypass the IP filter that ensures the request isn't going to an internal service using an IPv6 literal which maps to a private IPv4 address.

Vulnerable versions

This vulnerability is present in Ghost from v6.0.9 up to v6.21.0.

Patches

v6.21.1 contains a fix for this issue.

How to update

For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.

If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.

References

Ghost thanks l3tchupkt for disclosing this vulnerability responsibly.

For more information

If you have any questions or comments about this advisory, email us at security@ghost.org.

Affected versions

npm

PackageVulnerableFixed in
ghost
>= 6.0.9, < 6.21.1
6.21.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

ghost npm → 6.21.1

npm
npm install ghost@6.21.1
yarn
yarn add ghost@6.21.1
pnpm
pnpm add ghost@6.21.1

Severity breakdown

CVSS 3.1 5.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

Weakness

CWE-184: Incomplete List of Disallowed Inputs

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.

How to prevent it
  • Implementation: Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity. Ensure that you are using other protection mechanisms that only identify "good" input - such as lists of allowed inputs - and ensure that you are properly encoding your outputs.

CWE-918: Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-x3mg-q38v-m562
Ghost: Authorization Issue Allowed Author Role to Delete any Post
Medium Also affects ghost
GHSA-8575-cr6v-7jh4
Ghost: Stored XSS via SVG Uploads Bypassing Sanitization
High Also affects ghost
GHSA-r7f2-6fj8-6fg2
Ghost: Private IP Filtering Bypass via IPv6 Transition Addresses
Medium Also affects ghost
GHSA-322m-ff4g-9vx9
Ghost: Server-Side Request Forgery in Bookmark Fetching
Medium Also affects ghost
GHSA-fwh9-qg68-vxp4
Ghost: Regular Expression Denial of Service in Content Import
Medium Also affects ghost
GHSA-9m4w-fmjw-fvjq
Ghost: Regular Expression Denial of Service in External Media Inliner
Medium Also affects ghost
GHSA-hqq2-xqr2-fmx2
Ghost : Stored XSS via SVG Files in Content Imports
Medium Also affects ghost
GHSA-69qc-f5m6-889c
Ghost: Stored XSS via Embed Card Previews
High Also affects ghost
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor