# CVE-2026-26980: Ghost has a SQL Injection in its Content API

> Unauthenticated attackers can perform arbitrary database reads via SQL injection in the Ghost Content API.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Feb 2026
- **Updated:** 26 May 2026
- **Also known as:** BIT-ghost-2026-26980, GHSA-w52v-v783-gw97

## What is CVE-2026-26980?

CVE-2026-26980 is a critical SQL injection vulnerability in TryGhost Ghost, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ghost is a Node.js content management system. Versions 3.24.0 through 6.19.0 allow unauthenticated attackers to perform arbitrary reads from the database. This issue has been fixed in version 6.19.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

3 open source packages ship an affected version, including ghost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 3.24.0 | 6.19.1 |
| `ghost` | npm | From 3.24.0 | 6.19.1 |
| `ghost` | npm | From 3.24.0 | 6.19.1 |

Products: Ghost Ghost.

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

Upgrade ghost to 6.19.1 or later.

## Is CVE-2026-26980 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26980 exists.

Public exploit code:

- CVE-2026-26980 — Ghost CMS Content API SQL Injection Lab (unauthenticated blind SQLi via slug filter ordering) (github_poc): https://github.com/dinosn/ghost-cve-2026-26980
- CVE-2026-26980 - Ghost CMS Content API SQL Injection (github_poc): https://github.com/gagaltotal/CVE-2026-26980-Ghost-CMS-Api
- 💣 Exploit for CVE-2026-26980 — 👻 Ghost CMS Unauthenticated SQLi via Content API (github_poc): https://github.com/vognik/CVE-2026-26980
- Ghost Content API SQL Injection (github_poc): https://github.com/EQSTLab/CVE-2026-26980
- Ghost CMS Content API Blind SQL Injection (github_poc): https://github.com/n0bitaemon/CVE-2026-26980-PoC
- https://github.com/yym8538/CVE-2026-26980 (github_poc): https://github.com/yym8538/CVE-2026-26980

## Other vulnerabilities in TryGhost Ghost

- [CVE-2022-27139](https://insights.sbomify.com/CVE-2022-27139/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-28397](https://insights.sbomify.com/CVE-2022-28397/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-41654](https://insights.sbomify.com/CVE-2022-41654/): ghost vulnerable to unauthorized newsletter modification via improper access controls (critical 9.6)
- [CVE-2024-34451](https://insights.sbomify.com/CVE-2024-34451/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-23724](https://insights.sbomify.com/CVE-2024-23724/): Ghost has possible Cross-site Scripting issue (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26980 is a critical SQL injection vulnerability in TryGhost Ghost, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26980 exists.

Affected packages and fixed versions:
- ghost (Bitnami): affected from 3.24.0; fixed in 6.19.1
- ghost (npm): affected from 3.24.0; fixed in 6.19.1
- ghost (npm): affected from 3.24.0; fixed in 6.19.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-26980/ (Markdown: https://insights.sbomify.com/CVE-2026-26980/index.md)
```

## Sources

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

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