How severe is CVE-2026-103288?

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

Which packages are affected by CVE-2026-103288?

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

How do I fix CVE-2026-103288?

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

How do I detect CVE-2026-103288 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-103288 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-103288 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-103288 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-103288?

CVE-2026-103288 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th 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-103288?

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

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

CVE-2026-103288 was published on October 1, 2026 and was last updated on October 28, 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-103288 — ghost

Fix: TryGhost/Ghost#28297

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

Ghost 5.9.0 before 6.44.1 Authorization Bypass via Comment Like

Also known asBIT-ghost-2026-103288GHSA-qrh6-cwg3-343x

Published

Oct 1, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 26, 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-103288.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦ghost

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An input validation issue allowed members to delete comment likes / dislikes that they were not authorized to delete.

Vulnerable versions

This vulnerability is present in Ghost from v5.9.0 up to v6.44.1.

Patches

v6.44.1 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 Adel Assakaf and Arthur Gurunlian as well as Geoffrey Diederichs of Escape 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`	≥ 5.9.0&&< 6.44.1	6.44.1`npm install ghost@6.44.1`

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.44.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-103288 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 allowed members to delete comment likes / dislikes that they were not authorized to delete. ### Vulnerable versions This vulnerability is present in Ghost from v5.9.0 up to v6.44.1. ### Patches v6.44.1 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 [updating it to the l

O3 Security · Impact-Aware SCA

Is CVE-2026-103288 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works