# CVE-2026-103282: Ghost 0.5.0 before 6.23.0 Multiple Account Creation via Invite Token

> Attackers can exploit a race condition in Ghost's invitation system to create multiple user accounts from a single invite token, potentially gaining unauthorized access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** BIT-ghost-2026-103282, GHSA-fgrp-x4pm-v894, GHSA-vf9h-87xm-g767

## What is CVE-2026-103282?

CVE-2026-103282 is a medium-severity vulnerability in TryGhost Ghost, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ghost versions 0.5.0 before 6.23.0 contain a concurrency issue in the staff invitation acceptance mechanism that allows multiple accounts to be created from a single invite token. Attackers can exploit this race condition by submitting concurrent requests with the same invitation token to create duplicate user accounts.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 0.5.0 | 6.23.0 |

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

Upgrade ghost to 6.23.0 or later.

## Is CVE-2026-103282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103282 is a medium-severity vulnerability in TryGhost Ghost, published on 1 Oct 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-103282 in the wild and no public exploit code.

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

## Sources

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

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