CVE-2026-121664

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

GHSA-fr44-qgmq-4w24 ↗EUVD-2026-122474 ↗

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.
other:VS Code < 1.145.3
fixed in 1.145.3
ETK-2026-4218Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 53msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+26h43m
0
+2h
+4h
+6h
+8h
+10h

description

VS Code 1.145.2 and earlier render some extension Marketplace metadata as trusted Markdown. A malicious extension publisher could cause a command to run if a user views the affected extension details or hover UI and clicks a crafted link.

mitigation

Upgrade VS Code to version 1.145.3 or later. Until upgraded, avoid clicking links in extension names or descriptions and install extensions only from trusted publishers.

fixed in 1.145.3

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 18:23Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-10 18:23Z
  2. 2026-11-10 18:23Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4218",
  "cve_id": "CVE-2026-121664",
  "display_id": "CVE-2026-121664",
  "ghsa_id": "GHSA-fr44-qgmq-4w24",
  "euvd_id": "EUVD-2026-122474",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Trusted Markdown injection in VS Code extension metadata",
  "summary": "VS Code 1.145.2 and earlier render some extension Marketplace metadata as trusted Markdown. A malicious extension publisher could cause a command to run if a user views the affected extension details or hover UI and clicks a crafted link.",
  "mitigation": "Upgrade VS Code to version 1.145.3 or later. Until upgraded, avoid clicking links in extension names or descriptions and install extensions only from trusted publishers.",
  "vendor": "other",
  "product": "other:VS Code",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.145.3"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.145.3"
      ],
      "package_name": "VS Code",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.485632083333334,
  "t0_at": "2026-11-10T18:23:56.584000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T18:23:56.584000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T18:23:56.584000+00:00",
      "url": "https://github.com/microsoft/vscode/security/advisories/GHSA-fr44-qgmq-4w24"
    }
  }
}

published 2026-11-11 20:53Z
last change 2026-11-11 21:50Z

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.