CVE-2026-105642

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

GHSA-788w-68h3-cvxp ↗EUVD-2026-92621 ↗

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.56.0, < 6.67.0
fixed in 6.67.0
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-815, permanent identifier
pkg:npm/ghost
13d 15h 31msince last run
1h 47mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+52h43m
0
+2h
+4h
+6h
+8h
+10h

description

Ghost versions 6.56.0 through releases before 6.67.0 are affected by an SVG-handling flaw in a bundled image-processing component. A staff user, including a Contributor, can trigger command execution on the Ghost server by creating bookmark content tied to a site they control.

mitigation

Upgrade Ghost to version 6.67.0 or later. Until upgraded, restrict staff and Contributor access to trusted users and review bookmark creation activity.

fixed in 6.67.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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
1h 47m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 18:31Z
Δ 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 18:31Z
  2. 2026-10-05 18:31Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-815",
  "cve_id": "CVE-2026-105642",
  "display_id": "CVE-2026-105642",
  "ghsa_id": "GHSA-788w-68h3-cvxp",
  "euvd_id": "EUVD-2026-92621",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SVG processing command injection in Ghost",
  "summary": "Ghost versions 6.56.0 through releases before 6.67.0 are affected by an SVG-handling flaw in a bundled image-processing component. A staff user, including a Contributor, can trigger command execution on the Ghost server by creating bookmark content tied to a site they control.",
  "mitigation": "Upgrade Ghost to version 6.67.0 or later. Until upgraded, restrict staff and Contributor access to trusted users and review bookmark creation activity.",
  "vendor": "npm",
  "product": "Ghost",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.56.0, < 6.67.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "6.67.0"
      ],
      "package_name": "ghost",
      "purl": "pkg:npm/ghost"
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.1548,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 106.88138995,
  "t0_at": "2026-10-05T18:31:05.988000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T18:31:05.988000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T18:31:05.988000+00:00",
      "url": "https://github.com/TryGhost/Ghost/security/advisories/GHSA-788w-68h3-cvxp"
    }
  }
}

published 2026-10-06 22:03Z
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.