# CVE-2026-103268: Ghost 1.0.0 before 6.62.0 Suspension Bypass via Password Reset


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** BIT-ghost-2026-103268, GHSA-m47h-25hm-c3r9, GHSA-q734-xjgc-vpj9, MINI-p2mp-4295-455x

## What is CVE-2026-103268?

CVE-2026-103268 is a high-severity vulnerability in TryGhost Ghost, published on 1 Oct 2026. 

### Official description

Ghost versions before 6.62.0 contain an authentication bypass vulnerability that allows suspended staff users to reactivate their accounts through self-service password reset. Attackers with suspended staff credentials can perform password reset operations to regain active account access and restore their original privileges.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 1.0.0 | 6.62.0 |

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

Upgrade ghost to 6.62.0 or later.

## Is CVE-2026-103268 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103268 is a high-severity vulnerability in TryGhost Ghost, published on 1 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103268 in the wild and no public exploit code.

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

## Sources

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

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