Quick answers
- Is CVE-2026-105679 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105679 being exploited in the wild.
- How severe is CVE-2026-105679?
- High severity, with a CVSS score of 7.3, published 5 October 2026.
- Which products and versions are affected?
- ghost (npm) >= 6.22.1, < 6.64.0; TryGhost Ghost 6.22.1 through 6.63.x.
- Is there a fix for CVE-2026-105679?
- Yes: fixed in Ghost 6.64.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105679 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105679?
- Check whether you run ghost (npm) or TryGhost Ghost at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Ghost 6.64.0
Technical details
The vulnerability exists in Ghost versions 6.22.1 through 6.63.x where uploaded files served via the local storage adapter bypass content-type restrictions introduced in version 6.22.1. Files are served with content types derived from their extension instead of being forced to text/plain with X-Content-Type-Options: nosniff, allowing script execution in the browser. The attack requires staff-level upload privileges and affects sites using the default local storage configuration; the fix ensures all uploaded files are served with inert content types regardless of file extension.
Affected products
- TryGhost Ghost 6.22.1 through 6.63.x
Identifiers
- CVE-2026-105679
- GHSA-gfjp-2p8f-94qv
Timeline
- 2026-10-05: disclosed
- 2026-09-14: patched