# CVE-2026-22595: Ghost has Staff Token permission bypass

> Attackers with Staff Tokens can bypass authentication checks to access endpoints restricted to Staff Sessions, potentially exposing sensitive admin functions.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** BIT-ghost-2026-22595, GHSA-9xg7-mwmp-xmjx

## What is CVE-2026-22595?

CVE-2026-22595 is a high-severity missing authorization vulnerability in TryGhost Ghost, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ghost is a Node.js content management system. In versions 5.121.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's handling of Staff Token authentication allowed certain endpoints to be accessed that were only intended to be accessible via Staff Session authentication. External systems that have been authenticated via Staff Tokens for Admin/Owner-role users would have had access to these endpoints. This issue has been patched in versions 5.130.6 and 6.11.0.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 5.121.0 | 5.130.6, 6.11.0 |
| `ghost` | npm | From 5.105.0 | 5.130.6 |
| `ghost` | npm | From 5.105.0 | 5.130.6 |
| `ghost` | npm | From 6.0.0 | 6.11.0 |
| `ghost` | npm | From 6.0.0 | 6.11.0 |

Products: Ghost Ghost.

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

Upgrade ghost to a fixed version for your release line: 5.130.6 or 6.11.0.

## Is CVE-2026-22595 being exploited?

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

## 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-2026-26980](https://insights.sbomify.com/CVE-2026-26980/): Ghost has a SQL Injection in its Content API (critical 9.4)
- [CVE-2024-34451](https://insights.sbomify.com/CVE-2024-34451/): Security feature bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22595 is a high-severity missing authorization vulnerability in TryGhost Ghost, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22595 in the wild and no public exploit code.

Affected packages and fixed versions:
- ghost (Bitnami): affected from 5.121.0; fixed in 5.130.6, 6.11.0
- ghost (npm): affected from 5.105.0; fixed in 5.130.6
- ghost (npm): affected from 5.105.0; fixed in 5.130.6
- ghost (npm): affected from 6.0.0; fixed in 6.11.0
- ghost (npm): affected from 6.0.0; fixed in 6.11.0

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-22595/ (Markdown: https://insights.sbomify.com/CVE-2026-22595/index.md)
```

## Sources

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

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