Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 1.12% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-68785High confidence
Microsoft SQL Server Remote Code Execution Vulnerability
Microsoft · Microsoft SQL Server 2017 (CU 31)
4.9MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Microsoft SQL Server 2017 (CU 31) and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.
What
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
What
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Heap-based Buffer Overflow → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-122 ↗
CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Microsoft SQL Server 2025 (CU8): 17.0.0.0 < 17.0.4085.5
- Microsoft SQL Server 2017 (GDR): 14.0.0 < 14.0.2130.4
- Microsoft SQL Server 2019 (GDR): 15.0.0 < 15.0.2190.7
- Microsoft SQL Server 2025 for x64-based Systems (GDR): 17.0.1050.2 < 17.0.1135.8
- Microsoft SQL Server 2022 (GDR): 16.0.0 < 16.0.1200.5
- Microsoft SQL Server 2019 (CU 32): 15.0.0.0 < 15.0.4490.9
- Microsoft SQL Server 2017 (CU 31): 14.0.0 < 14.0.3550.4
- Microsoft SQL Server 2022 (CU 26): 16.0.0.0 < 16.0.4275.2
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Sept 2026 · Last source change 1 Oct 2026, 22:52 UTC · CWE-122 · Heap-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-09
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-73189
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added patch: msrc.microsoft.com/CVE-2026-68785; added remediation: msrc.microsoft.com/CVE-2026-68785.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- patch: msrc.microsoft.com/CVE-2026-68785 · remediation: msrc.microsoft.com/CVE-2026-68785
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Microsoft SQL Server 2017 (CU 31): 14.0.0 < 14.0.3550.4; Microsoft SQL Server 2017 (GDR): 14.0.0 < 14.0.2130.4; Microsoft SQL Server 2019 (CU 32): 15.0.0.0 < 15.0.4490.9; Microsoft SQL Server 2019 (GDR): 15.0.0 < 15.0.2190.7; Microsoft SQL Server 2022 (CU 26): 16.0.0.0 < 16.0.4275.2; Microsoft SQL Server 2022 (GDR): 16.0.0 < 16.0.1200.5; Microsoft SQL Server 2025 (CU8): 17.0.0.0 < 17.0.4085.5; Microsoft SQL Server 2025 for x64-based Systems (GDR): 17.0.1050.2 < 17.0.1135.8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft SQL Server 2017 (CU 31): 14.0.0 < 14.0.3550.4; Microsoft SQL Server 2017 (GDR): 14.0.0 < 14.0.2130.4; Microsoft SQL Server 2019 (CU 32): 15.0.0.0 < 15.0.4490.9; Microsoft SQL Server 2019 (GDR): 15.0.0 < 15.0.2190.7; Microsoft SQL Server 2022 (CU 26): 16.0.0.0 < 16.0.4275.2; Microsoft SQL Server 2022 (GDR): 16.0.0 < 16.0.1200.5; Microsoft SQL Server 2025 (CU8): 17.0.0.0 < 17.0.4085.5; Microsoft SQL Server 2025 for x64-based Systems (GDR): 17.0.1050.2 < 17.0.1135.8 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.secure@microsoft.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 14.0.0 < 14.0.3550.4; 14.0.0 < 14.0.2130.4; 15.0.0.0 < 15.0.4490.9; 15.0.0 < 15.0.2190.7; 16.0.0.0 < 16.0.4275.2; 16.0.0 < 16.0.1200.5; 17.0.0.0 < 17.0.4085.5; 17.0.1050.2 < 17.0.1135.8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft SQL Server 2017 (CU 31): 14.0.0 < 14.0.3550.4; Microsoft SQL Server 2017 (GDR): 14.0.0 < 14.0.2130.4; Microsoft SQL Server 2019 (CU 32): 15.0.0.0 < 15.0.4490.9; Microsoft SQL Server 2019 (GDR): 15.0.0 < 15.0.2190.7; Microsoft SQL Server 2022 (CU 26): 16.0.0.0 < 16.0.4275.2; Microsoft SQL Server 2022 (GDR): 16.0.0 < 16.0.1200.5; Microsoft SQL Server 2025 (CU8): 17.0.0.0 < 17.0.4085.5; Microsoft SQL Server 2025 for x64-based Systems (GDR): 17.0.1050.2 < 17.0.1135.8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- ENISA EUVD mappingEUVD-2026-73189 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-73189"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.