# CVE-2026-25552: Ghost CLI < 1.30.1 IP Spoofing via X-Forwarded-For Header

> Attackers can bypass rate-limiting controls in Ghost CLI by spoofing IP addresses via the X-Forwarded-For header in misconfigured Nginx setups.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** BIT-ghost-2026-25552, GHSA-wjx2-9fpq-8997

## What is CVE-2026-25552?

CVE-2026-25552 is a medium-severity vulnerability in TryGhost Ghost-CLI, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ghost CLI before 1.30.1 contains an IP spoofing vulnerability that allows unauthenticated remote attackers to bypass rate-limiting controls by manipulating the X-Forwarded-For header through a misconfigured Nginx configuration. Attackers can append attacker-controlled values to the header chain using the $proxy_add_x_forwarded_for directive to present an arbitrary IP address, circumventing Ghost's rate-limiting mechanisms on self-hosted instances.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2026-25552?

1 open source package ship an affected version, including ghost.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | All versions | 1.30.1 |

## How do I fix CVE-2026-25552?

Upgrade ghost to 1.30.1 or later.

## Is CVE-2026-25552 being exploited?

There is no known exploitation of CVE-2026-25552 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25552 and fix it if it is affected.

What it is: CVE-2026-25552 is a medium-severity vulnerability in TryGhost Ghost-CLI, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25552 in the wild and no public exploit code.

Affected packages and fixed versions:
- ghost (Bitnami): affected all versions; fixed in 1.30.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25552/ (Markdown: https://insights.sbomify.com/CVE-2026-25552/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25552
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25552
- OSV: https://osv.dev/vulnerability/CVE-2026-25552

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25552/
Summaries are generated and may contain mistakes; the official description above is the record.