CVE-2026-81356

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this week

Also known asEUVD-2026-73330 (ENISA EUVD)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Inconsistent interpretation of http requests ('http request/response smuggling') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 8, 2026

Last Modified

October 31, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81356

Vendor Advisories for CVE-2026-81356(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 69× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 180 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-10-31 16:21 UTCVendor advisory
  4. 2026-10-30 21:56 UTCEG score recompute
  5. 2026-10-30 21:56 UTCVendor advisory
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-10-28 06:45 UTCEG score recompute
  10. 2026-10-28 06:45 UTCVendor advisory
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-25 13:58 UTCEG score recompute
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-21 11:42 UTCEG score recompute
  20. 2026-10-21 11:42 UTCVendor advisory
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-18 03:09 UTCEG score recompute
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-14 23:25 UTCEG score recompute
  4. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-13 06:20 UTCEG score recompute
  7. 2026-10-13 06:20 UTCVendor advisory
  8. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-12 14:56 UTCEG score recompute
  10. 2026-10-11 19:20 UTCEG score recompute
  11. 2026-10-11 16:37 UTCEG score recompute
  12. 2026-10-11 15:46 UTCVendor advisory
  13. 2026-10-11 13:55 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-10 08:53 UTCVendor advisory
  17. 2026-10-09 21:27 UTCEG score recompute
  18. 2026-10-09 21:27 UTCVendor advisory
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-09 06:35 UTCVendor advisory
  21. 2026-10-08 19:00 UTCEG score recompute
  22. 2026-10-08 19:00 UTCVendor advisory
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-08 03:21 UTCEG score recompute
  25. 2026-10-08 03:21 UTCVendor advisory
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-07 15:57 UTCVendor advisory
  28. 2026-10-07 06:15 UTCVendor advisory
  29. 2026-10-06 18:51 UTCEG score recompute
  30. 2026-10-06 18:51 UTCVendor advisory
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-06 07:27 UTCVendor advisory
  33. 2026-10-05 20:04 UTCEG score recompute
  34. 2026-10-05 20:04 UTCVendor advisory
  35. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-05 08:41 UTCEG score recompute
  37. 2026-10-05 08:41 UTCVendor advisory
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-04 21:17 UTCVendor advisory
  40. 2026-10-04 09:53 UTCVendor advisory
  41. 2026-10-03 22:21 UTCEG score recompute
  42. 2026-10-03 22:21 UTCVendor advisory
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-10-03 10:57 UTCVendor advisory
  45. 2026-10-02 22:29 UTCEG score recompute
  46. 2026-10-02 22:29 UTCVendor advisory
  47. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-10-02 11:04 UTCVendor advisory
  49. 2026-10-01 23:41 UTCEG score recompute
  50. 2026-10-01 23:41 UTCVendor advisory
  51. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-10-01 14:47 UTCVendor advisory
  53. 2026-10-01 03:23 UTCVendor advisory
  54. 2026-09-30 16:00 UTCEG score recompute
  55. 2026-09-30 16:00 UTCVendor advisory
  56. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  57. 2026-09-30 11:08 UTCVendor advisory
  58. 2026-09-29 23:15 UTCEG score recompute
  59. 2026-09-29 23:15 UTCVendor advisory
  60. 2026-09-29 06:17 UTCEG score recompute
  61. 2026-09-29 06:17 UTCVendor advisory
  62. 2026-09-28 18:54 UTCEG score recompute
  63. 2026-09-28 18:54 UTCVendor advisory
  64. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  65. 2026-09-28 07:03 UTCVendor advisory
  66. 2026-09-27 19:40 UTCEG score recompute
  67. 2026-09-27 19:40 UTCVendor advisory
  68. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  69. 2026-09-27 08:16 UTCVendor advisory
  70. 2026-09-26 20:52 UTCEG score recompute
  71. 2026-09-26 20:52 UTCVendor advisory
  72. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  73. 2026-09-26 09:25 UTCEG score recompute
  74. 2026-09-26 09:25 UTCVendor advisory
  75. 2026-09-25 22:01 UTCVendor advisory

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81356?
CVE-2026-81356 is a high-severity vulnerability; its CVE record was published on September 8, 2026. Inconsistent interpretation of http requests ('http request/response smuggling') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-81356 made public?
CVE-2026-81356 was made public on September 8, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 8, 2026. EchelonGraph's copy of the record carries a last-modified date of October 31, 2026; the record at its source may have been updated since.
Is CVE-2026-81356 actively exploited?
CVE-2026-81356 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81356?
CVE-2026-81356 has a CVSS base score of 8.2 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-81356?
A fix for CVE-2026-81356 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81356 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81356

Explore →

Is Your Infrastructure Affected by CVE-2026-81356?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs