# CVE-2026-103283: Ghost 6.20.0 before 6.57.1 Authentication Bypass via Session Handling

> Authenticated staff users can bypass two-factor authentication and impersonate other staff members to gain unauthorized administrative access.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:** 6 Oct 2026
- **Also known as:** BIT-ghost-2026-103283, GHSA-q55r-w7fh-rmh6, GHSA-xwp3-2mhg-j9rp, MINI-88fw-6f3q-qvcp

## What is CVE-2026-103283?

CVE-2026-103283 is a high-severity authentication bypass 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 6.20.0 before 6.57.1 contain a session handling vulnerability that allows authenticated staff users to log in as any other staff user with only the password, bypassing two-factor authentication. Attackers with valid staff credentials can exploit improper session management to impersonate other staff members and gain unauthorized access to administrative functions.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | From 6.20.0 | 6.57.1 |

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

Upgrade ghost to 6.57.1 or later.

## Is CVE-2026-103283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103283 is a high-severity authentication bypass 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-103283 in the wild and no public exploit code.

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

## Sources

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

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