Buffer over-read in SQL Server allows an authorized attacker to disclose information over a network.
CVE-2026-73029
Score 6.5 from GitHub Security Advisory published 2026-09-08. the CNA's CVSS baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 30(Track)EG Risk 30/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 computedSeverity65% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 53%
- KEV
- Not listed
Published
September 8, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 8, 2026Security 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-73029Vendor Advisories for CVE-2026-73029(2)
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 40× in last 7d / 68× 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.
- 2026-09-19 20:35 UTCEG score recompute
- 2026-09-19 20:35 UTCVendor advisory
- 2026-09-19 20:35 UTCGHSA enrichment
- 2026-09-18 21:07 UTCEG score recompute
- 2026-09-18 21:07 UTCVendor advisory
- 2026-09-18 21:07 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:13 UTCVendor advisory
- 2026-09-18 14:13 UTCGHSA enrichment
- 2026-09-17 23:08 UTCVendor advisory
- 2026-09-17 23:08 UTCGHSA enrichment
- 2026-09-17 20:12 UTCVendor advisory
- 2026-09-17 20:12 UTCGHSA enrichment
- 2026-09-17 19:55 UTCEG score recompute
- 2026-09-17 19:55 UTCVendor advisory
- 2026-09-17 19:55 UTCGHSA enrichment
- 2026-09-16 22:12 UTCEG score recompute
- 2026-09-16 22:12 UTCVendor advisory
- 2026-09-16 22:12 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 22:48 UTCVendor advisory
- 2026-09-15 22:48 UTCGHSA enrichment
- 2026-09-15 18:01 UTCEG score recompute
- 2026-09-15 18:01 UTCVendor advisory
Show 43 moreShow fewer
- 2026-09-15 18:01 UTCGHSA enrichment
- 2026-09-15 16:12 UTCEG score recompute
- 2026-09-15 16:12 UTCVendor advisory
- 2026-09-15 16:12 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 22:58 UTCVendor advisory
- 2026-09-14 22:58 UTCGHSA enrichment
- 2026-09-14 17:50 UTCVendor advisory
- 2026-09-14 17:50 UTCGHSA enrichment
- 2026-09-13 21:57 UTCEG score recompute
- 2026-09-13 21:57 UTCVendor advisory
- 2026-09-13 21:57 UTCGHSA enrichment
- 2026-09-12 22:29 UTCEG score recompute
- 2026-09-12 22:29 UTCVendor advisory
- 2026-09-12 22:29 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 23:00 UTCVendor advisory
- 2026-09-11 23:00 UTCGHSA enrichment
- 2026-09-11 19:44 UTCVendor advisory
- 2026-09-11 19:44 UTCGHSA enrichment
- 2026-09-11 17:04 UTCEG score recompute
- 2026-09-11 17:04 UTCVendor advisory
- 2026-09-11 17:04 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 21:54 UTCEG score recompute
- 2026-09-10 21:54 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 22:25 UTCGHSA enrichment
- 2026-09-09 20:12 UTCVendor advisory
- 2026-09-09 20:12 UTCGHSA enrichment
- 2026-09-09 00:08 UTCEG score recompute
- 2026-09-09 00:08 UTCVendor advisory
- 2026-09-09 00:08 UTCGHSA enrichment
- 2026-09-08 21:50 UTCEG score recompute
- 2026-09-08 21:50 UTCVendor advisory
- 2026-09-08 21:50 UTCGHSA enrichment
- 2026-09-08 20:42 UTCEG score recompute
- 2026-09-08 20:42 UTCGHSA enrichment
- 2026-09-08 18:58 UTCEG score recompute
- 2026-09-08 18:58 UTCGHSA enrichment
- 2026-09-08 17:56 UTCEG score recompute
- 2026-09-08 17:56 UTCVendor advisory
- 2026-09-08 17:25 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-126
- CVE-2017-17772EG 9.8CRITICAL
- CVE-2022-1927NVD 7.8EG 9.8CRITICAL
- CVE-2019-3563EG 9.8CRITICAL
- CVE-2018-14790EG 9.8EPSS p92CRITICAL
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2021-34584EG 9.1CRITICAL
- CVE-2019-11036EG 9.1EPSS p94CRITICAL
- CVE-2022-2175NVD 7.8EG 8.8HIGH
- CVE-2022-20823EG 8.6HIGH
- CVE-2022-20714EG 8.6HIGH
Frequently asked(5)
What is CVE-2026-73029?
When was CVE-2026-73029 disclosed?
Is CVE-2026-73029 actively exploited?
What is the CVSS score of CVE-2026-73029?
How do I remediate CVE-2026-73029?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73029
Is Your Infrastructure Affected by CVE-2026-73029?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.