CVE-2026-26980: Ghost Content API SQL injection
CVE-2026-26980 (Ghost Content API SQL injection) is a sql injection (unauthenticated database read) vulnerability in ghost (npm). As of 2026-06-18 it carries an elevated 16.5% probability of exploitation in the next 30 days (EPSS). It is fixed in 6.19.1 — if you depend on an earlier version, upgrade.
| Severity | Critical |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L |
| EPSS (exploit probability, 30d) | 16.5% · 97th percentile |
| Vulnerability type | SQL Injection (unauthenticated database read) |
| Affected package | ghost (npm) |
| Fixed in | 6.19.1 |
What is CVE-2026-26980?
Ghost, a popular Node.js content-management system, contained a SQL injection in its Content API affecting versions 3.24.0 through 6.19.0, letting unauthenticated attackers perform arbitrary reads from the database. It was reported as exploited in the wild. Fixed in 6.19.1.
Is CVE-2026-26980 exploitable?
CVE-2026-26980 has an EPSS score of 16.5% (97th percentile), meaning an elevated 16.5% probability of exploitation in the next 30 days. Its CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L, which scores as Critical severity. It is a sql injection (unauthenticated database read) issue.
What is the EPSS score for CVE-2026-26980?
As of 2026-06-18, the EPSS exploit-prediction score for CVE-2026-26980 is 16.5% (97th percentile). EPSS estimates the probability that a vulnerability will be exploited in the wild within the next 30 days and is recomputed daily by FIRST.org.
How do I fix CVE-2026-26980?
Upgrade ghost to 6.19.1 or later. Ghost, a popular Node.js content-management system, contained a SQL injection in its Content API affecting versions 3.24.0 through 6.19.0, letting unauthenticated attackers perform arbitrary reads from the database. It was reported as exploited in the wild. Fixed in 6.19.1.
Am I affected by CVE-2026-26980?
You are affected if your project (directly or transitively) depends on a vulnerable version of ghost in the npm ecosystem. Check your lockfile for the resolved version, or scan automatically with VulnFeed.
Check your own project automatically
Don't eyeball every dependency by hand. VulnFeed reads your lockfile, checks it against the same advisory data, and ranks findings by EPSS — free, no signup (10 scans/day):
curl -s https://vulnfeed-api.novadyne.ai/vulnscan/query \
-H 'content-type: application/json' \
-d '{"ecosystem":"npm","package":"PKG","version":"VERSION"}'
Or run it inside Claude Code with no API key — uvx vulnfeed-mcp — and just ask "scan this project for vulnerabilities."
Data sources: vulnerability metadata from OSV.dev and the National Vulnerability Database; exploit-probability (EPSS) from FIRST.org (recomputed daily; EPSS data shown here as of 2026-06-18). Page generated 2026-06-18.