# CVE-2026-103289: Ghost 5.9.0 before 6.44.1 Authorization Bypass via Comments

> Authenticated members can access restricted comment data due to an input validation flaw in the comments feature.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** GHSA-83rv-pxjq-8h5x

## What is CVE-2026-103289?

CVE-2026-103289 is a high-severity missing authorization 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 from 5.9.0 before 6.44.1 contains an input validation issue in the comments feature that allows authenticated members to access comments they are not authorized to view, resulting in disclosure of restricted comment data.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

Upgrade to a fixed version.

## Is CVE-2026-103289 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: TryGhost Ghost. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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