GHSA-ch52-px8q-f22j: SSRF

Published Aug 4, 2026
·
Updated

Impact

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.

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.

Workarounds

If upgrading immediately is not possible, operators can reduce exposure by preventing the Ghost server from reaching sensitive internal ranges at the network layer — for example, egress firewall rules that block the Ghost process from initiating connections to RFC1918 networks, loopback, link-local (including 169.254.169.254) and any other internal service ranges. Disabling features that trigger outbound fetches (oEmbed, webmentions, recommendations) will further limit the attack surface but does not remove the underlying issue.

References

Ghost thanks Oluwaseun Esther Folorunsho, Lakshmikanthan K (@l3tchupkt), Offgrid Security, and Baki 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 Software

1 affected componentFixes available
npm/ghost>=6.0.9<6.21.1
6.21.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/ghost to a version that resolves this vulnerability.

    Fixed in 6.21.2
  2. Upgrade

    Upgrade Ghost to a version that resolves this vulnerability.

    Fixed in v6.21.1
  3. Compensating control

    For self-hosted Ghost, add egress firewall rules to prevent the Ghost process from initiating outbound connections to sensitive internal ranges (block RFC1918 networks, loopback, and link-local including 169.254.169.254, plus any other internal service ranges) to reduce exposure if upgrading is not immediately possible.

Event History

Aug 4, 2026
Advisory Published
via GitHub·09:24 PM
Data Sourced
via GitHub·09:24 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of GHSA-ch52-px8q-f22j?

The severity of GHSA-ch52-px8q-f22j is medium with a score of 4.

2

How do I fix GHSA-ch52-px8q-f22j?

To fix GHSA-ch52-px8q-f22j, update to the latest version of Ghost where this vulnerability is resolved.

3

What type of vulnerability is GHSA-ch52-px8q-f22j?

GHSA-ch52-px8q-f22j is a Server-Side Request Forgery (SSRF) vulnerability.

4

What does GHSA-ch52-px8q-f22j allow an attacker to do?

GHSA-ch52-px8q-f22j allows an attacker to bypass private-IP checks, coercing the Ghost server to reach internal network hosts.

5

In which software is GHSA-ch52-px8q-f22j found?

GHSA-ch52-px8q-f22j is present in the Ghost content management system, specifically in the npm package.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203