# CVE-2026-105683: Ghost: Path Traversal Vulnerability in Ghost ImageSize Service

> Staff users can access local files outside intended directories due to input validation flaws in the Ghost CMS image service.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 8 Oct 2026

## What is CVE-2026-105683?

CVE-2026-105683 is a low-severity path traversal vulnerability in TryGhost Ghost, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Ghost is a Node.js content management system. From 6.14.0 until 6.27.0, an input validation issue may have allowed staff users to access local files outside the intended data storage directories on the server. This issue is fixed in version 6.27.0.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

Upgrade to a fixed version.

## Is CVE-2026-105683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105683 is a low-severity path traversal vulnerability in TryGhost Ghost, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105683 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-105683/ (Markdown: https://insights.sbomify.com/CVE-2026-105683/index.md)
```

## Sources

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

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