CVE-2026-105677

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

EUVD-2026-92767 ↗

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.
npm 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-843, permanent identifier
pkg:npm/ghost
13d 22h 57msince last run
2h 55mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+35h31m
0
+2h
+4h
+6h
+8h
+10h

description

Ghost versions starting with 6.10.3 and preceding 6.64.0 improperly process translation files in themes. An authenticated Administrator able to install a malicious theme can run code on the server.

mitigation

Upgrade Ghost to version 6.64.0 or later. Until the upgrade is complete, restrict Administrator access and limit who can install or modify 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.
–
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.52%43rd percentile
agent run time
2h 55m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 19:18Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-05 19:18Z
  2. 2026-10-05 19:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-843",
  "cve_id": "CVE-2026-105677",
  "display_id": "CVE-2026-105677",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-92767",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated code execution in Ghost theme translation loading",
  "summary": "Ghost versions starting with 6.10.3 and preceding 6.64.0 improperly process translation files in themes. An authenticated Administrator able to install a malicious theme can run code on the server.",
  "mitigation": "Upgrade Ghost to version 6.64.0 or later. Until the upgrade is complete, restrict Administrator access and limit who can install or modify themes.",
  "vendor": "npm",
  "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": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0052,
  "epss_percentile": 0.4326,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 174.96718476666666,
  "t0_at": "2026-10-05T19:18:41.926000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T19:18:41.926000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T19:18:41.926000+00:00",
      "url": "https://github.com/TryGhost/Ghost/security/advisories/GHSA-jj74-hc2q-xrvm"
    }
  }
}

published 2026-10-07 03:54Z
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.