How severe is CVE-2026-103290?

No CVSS score has been assigned to CVE-2026-103290 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-103290?

CVE-2026-103290 affects the following packages: ghost (npm). Ecosystems affected: npm.

How do I fix CVE-2026-103290?

Update ghost to 6.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-103290 is resolved across your whole dependency graph.

How do I detect CVE-2026-103290 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-103290 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-103290 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-103290 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-103290?

CVE-2026-103290 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-103290?

CVE-2026-103290 is classified as CWE-35 (CWE-35). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-103290 published, and has it been updated?

CVE-2026-103290 was published on October 1, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-103290 — ghost

Fix: TryGhost/Ghost#27217

CVE-2026-103290 is a CWE-35 vulnerability in ghost. A fix is available for ghost — see the affected versions and patch details below.

Ghost 6.14.0 before 6.27.0 Path Traversal via ImageSize

Also known asBIT-ghost-2026-103290BIT-ghost-2026-105683CVE-2026-105683 GHSA-83rp-q473-j88c

Published

Oct 1, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-103290.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

8other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ghostnpm

11Kdownloads / week

Description

Impact

An input validation issue may have allowed staff users to access local files outside the intended data storage directories on the server.

Vulnerable versions

This vulnerability is present in Ghost from v6.14.0 up to v6.27.0.

Patches

v6.27.0 contains a fix for this issue.

How to update

For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.

If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.

References

Ghost thanks l3tchupkt and [email protected] for disclosing this vulnerability responsibly.

For more information

If you have any questions or comments about this advisory, email us at [email protected].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ghost`	≥ 6.14.0&&< 6.27.0	6.27.0`npm install ghost@6.27.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ghost to 6.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-103290 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact An input validation issue may have allowed staff users to access local files outside the intended data storage directories on the server. ### Vulnerable versions This vulnerability is present in Ghost from v6.14.0 up to v6.27.0. ### Patches v6.27.0 contains a fix for this issue. ### How to update For self-hosters using Docker, find [Docker's official Ghost image here](https://hub.docker.com/_/ghost). Updating a Docker-based Ghost instance [is documented here](https://docs.ghost.org/install/docker#updating-ghost). If your Ghost is a Ghost-CLI install see our documentation on

O3 Security · Impact-Aware SCA

Is CVE-2026-103290 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works