CVE-2026-71328

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-71328(2)

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

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.DiaSymReader.Native—18.9.0-beta1.26405.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-21 00:49 UTCEG score recompute
  2. 2026-09-21 00:49 UTCVendor advisory
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 11:53 UTCVendor advisory
  5. 2026-09-19 22:46 UTCEG score recompute
  6. 2026-09-19 22:46 UTCVendor advisory
  7. 2026-09-19 09:51 UTCVendor advisory
  8. 2026-09-18 20:56 UTCEG score recompute
  9. 2026-09-18 20:56 UTCVendor advisory
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 14:04 UTCVendor advisory
  12. 2026-09-18 12:23 UTCVendor advisory
  13. 2026-09-17 23:27 UTCVendor advisory
  14. 2026-09-17 20:06 UTCEG score recompute
  15. 2026-09-17 20:06 UTCVendor advisory
  16. 2026-09-17 11:03 UTCVendor advisory
  17. 2026-09-16 22:08 UTCEG score recompute
  18. 2026-09-16 22:08 UTCVendor advisory
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 11:48 UTCEG score recompute
  21. 2026-09-16 11:48 UTCVendor advisory
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 22:53 UTCVendor advisory
  24. 2026-09-15 17:49 UTCVendor advisory
  25. 2026-09-15 11:59 UTCEG score recompute
Show 46 more
  1. 2026-09-15 11:59 UTCVendor advisory
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 23:04 UTCVendor advisory
  4. 2026-09-14 17:35 UTCVendor advisory
  5. 2026-09-14 15:09 UTCVendor advisory
  6. 2026-09-14 02:14 UTCEG score recompute
  7. 2026-09-14 02:14 UTCVendor advisory
  8. 2026-09-13 13:19 UTCVendor advisory
  9. 2026-09-13 00:24 UTCEG score recompute
  10. 2026-09-13 00:24 UTCVendor advisory
  11. 2026-09-12 15:02 UTCEPSS rescore
  12. 2026-09-12 11:28 UTCVendor advisory
  13. 2026-09-11 22:33 UTCEG score recompute
  14. 2026-09-11 22:33 UTCVendor advisory
  15. 2026-09-11 20:47 UTCEG score recompute
  16. 2026-09-11 20:47 UTCVendor advisory
  17. 2026-09-11 19:58 UTCVendor advisory
  18. 2026-09-11 16:58 UTCEG score recompute
  19. 2026-09-11 16:58 UTCVendor advisory
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 12:27 UTCEG score recompute
  22. 2026-09-10 10:50 UTCEG score recompute
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-09 21:47 UTCVendor advisory
  25. 2026-09-09 19:59 UTCEG score recompute
  26. 2026-09-09 19:59 UTCVendor advisory
  27. 2026-09-09 10:26 UTCEG score recompute
  28. 2026-09-09 10:26 UTCVendor advisory
  29. 2026-09-09 10:26 UTCGHSA enrichment
  30. 2026-09-09 10:02 UTCVendor advisory
  31. 2026-09-09 10:02 UTCGHSA enrichment
  32. 2026-09-09 04:29 UTCVendor advisory
  33. 2026-09-09 04:29 UTCGHSA enrichment
  34. 2026-09-09 04:04 UTCEG score recompute
  35. 2026-09-09 04:04 UTCVendor advisory
  36. 2026-09-09 04:04 UTCGHSA enrichment
  37. 2026-09-08 23:54 UTCEG score recompute
  38. 2026-09-08 23:54 UTCVendor advisory
  39. 2026-09-08 23:54 UTCGHSA enrichment
  40. 2026-09-08 18:53 UTCGHSA enrichment
  41. 2026-09-08 18:38 UTCEG score recompute
  42. 2026-09-08 18:38 UTCVendor advisory
  43. 2026-09-08 18:38 UTCGHSA enrichment
  44. 2026-09-08 17:41 UTCEG score recompute
  45. 2026-09-08 17:41 UTCVendor advisory
  46. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71328?
CVE-2026-71328 is a high vulnerability published on September 8, 2026. Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.
When was CVE-2026-71328 disclosed?
CVE-2026-71328 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71328 actively exploited?
CVE-2026-71328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.0% of all scored CVEs.
What is the CVSS score of CVE-2026-71328?
CVE-2026-71328 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-71328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71328, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71328

Explore →

Is Your Infrastructure Affected by CVE-2026-71328?

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

Start Free Scan →Browse All CVEs