CVE-2026-121662

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

GHSA-fp22-hgv9-mq6q ↗EUVD-2026-122472 ↗

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-4216Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 52msince last run
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+26h28m
0
+2h
+4h
+6h
+8h
+10h

description

VS Code 1.145.2 and earlier can improperly merge workspace configuration, allowing prototype pollution to bypass Restricted Mode protections. An attacker who persuades a user to open a malicious workspace may cause that workspace's MCP server to start without a trust decision.

mitigation

Update VS Code to version 1.145.3 or later. Until updates are deployed, do not open workspaces from untrusted sources.

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.
–
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
<1m
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

No artifact: no remotely reachable path found.

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-121662

{
  "etk_id": "ETK-2026-4216",
  "cve_id": "CVE-2026-121662",
  "display_id": "CVE-2026-121662",
  "ghsa_id": "GHSA-fp22-hgv9-mq6q",
  "euvd_id": "EUVD-2026-122472",
  "status": "rejected_out_of_scope",
  "anchor_state": "anchored",
  "title": "Workspace Trust bypass through prototype pollution in VS Code",
  "summary": "VS Code 1.145.2 and earlier can improperly merge workspace configuration, allowing prototype pollution to bypass Restricted Mode protections. An attacker who persuades a user to open a malicious workspace may cause that workspace's MCP server to start without a trust decision.",
  "mitigation": "Update VS Code to version 1.145.3 or later. Until updates are deployed, do not open workspaces from untrusted sources.",
  "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.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 0.20278518333333334,
  "t0_at": "2026-11-10T18:23:55.463000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T18:23:55.463000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T18:23:55.463000+00:00",
      "url": "https://github.com/microsoft/vscode/security/advisories/GHSA-fp22-hgv9-mq6q"
    }
  }
}

published 2026-11-11 20:51Z
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.