← console
voxell vciy

CVE-2025-55319: Agentic AI and Visual Studio Code Remote Code Execution Vulnerability

RECORD

Description revised (poc_count, poc_public, poc_url). The record changed; nothing in the observed threat did.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to 1.104.0 or later CVE record
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

Ai command injection in Agentic AI and Visual Studio Code allows an unauthorized attacker to execute code over a network.

weakness
CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
affected
Microsoft Visual Studio Code
published ranges
microsoft visual studio code < 1.104.0
fixed in
1.104.0
severity
8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
assigned by
microsoft
published
2025-09-12

check us msrc.microsoft.com

Exploit code held, dated

exploit code
1 public proof-of-concept repository, first seen 2026-07-11 (PoC-in-GitHub).

What moved held, dated

dateEPSSevent
12 Sep 20250.00078
13 Sep 20250.00083
18 Sep 20250.00065
25 Sep 20250.00072
15 Jun 20260.00857scoring model v2026.06.15
20 Jun 20260.00849
13 Aug 20260.00911
4 Sep 20260.00918

19 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-09-04 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 1.104.0. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-55319', '2026-11-02T23:59:59.999999Z', now());