CVE-2026-104418

waiting for further signalsZero needs more public information before it can validate it.

GHSA-5pc5-4pc7-5x44 ↗EUVD-2026-91429 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
TryGhost Ghost >= 6.10.3, < 6.64.0
fixed in 6.64.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-334, permanent identifier
pkg:npm/ghost
19d 02h 04msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h57m
0
+4h
+6h
+8h
+10h
+12h

description

Ghost versions 6.10.3 through 6.63.x are affected when administrators can upload themes. An attacker with administrator access may execute code on the Ghost server by supplying a crafted theme with malicious translation resources.

mitigation

Upgrade the Ghost npm package to version 6.64.0 or later. Until upgraded, restrict administrator access and prevent untrusted users from uploading themes.

fixed in 6.64.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.65%50th percentile
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 11:38Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 11:38Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-104418

{
  "etk_id": "ETK-2026-334",
  "cve_id": "CVE-2026-104418",
  "display_id": "CVE-2026-104418",
  "ghsa_id": "GHSA-5pc5-4pc7-5x44",
  "euvd_id": "EUVD-2026-91429",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code execution through Ghost theme translation loading",
  "summary": "Ghost versions 6.10.3 through 6.63.x are affected when administrators can upload themes. An attacker with administrator access may execute code on the Ghost server by supplying a crafted theme with malicious translation resources.",
  "mitigation": "Upgrade the Ghost npm package to version 6.64.0 or later. Until upgraded, restrict administrator access and prevent untrusted users from uploading themes.",
  "vendor": "TryGhost",
  "product": "Ghost",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.10.3, < 6.64.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "6.64.0"
      ],
      "package_name": "ghost",
      "purl": "pkg:npm/ghost"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0065,
  "epss_percentile": 0.5045,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.770576966666667,
  "t0_at": "2026-10-02T11:38:00.453000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T11:38:00.453000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T11:38:00.453000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104418"
    }
  }
}

published 2026-10-02 12:29Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.