← back to feed
CVE-2026-94512

CVE-2026-94512

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qc5v-8339-5w6j ↗EUVD-2026-100619 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Microsoft SQL Server 2017 (GDR) >= 14.0.0, < 14.0.2140.2; >= 14.0.3006.16, < 14.0.3560.2; >= 15.0.0, < 15.0.2200.2; >= 15.0.4003.23, < 15.0.4500.2; >= 16.0.0, < 16.0.1210.3; >= 16.0.4003.1, < 16.0.4305.5; >= 17.0.4006.2, < 17.0.5015.4; >= 17.0.1050.2, < 17.0.1145.4
fixed in 14.0.2140.2, 14.0.3560.2, 15.0.2200.2, 15.0.4500.2, 16.0.1210.3, 16.0.4305.5, 17.0.5015.4, 17.0.1145.4
ETK-2026-1529Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.8cna vendorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5d 02h 00msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+55h06m
0
+2h
+4h
+6h
+8h
+10h

description

Affected Microsoft SQL Server 2017, 2019, 2022, and 2025 servicing branches contain a heap memory overflow flaw. An authenticated attacker with network access may be able to execute code on the SQL Server host.

mitigation

Apply the relevant SQL Server security update: update 2017 GDR to 14.0.2140.2 or CU31 to 14.0.3560.2; 2019 GDR to 15.0.2200.2 or CU32 to 15.0.4500.2; 2022 GDR to 16.0.1210.3 or CU27 to 16.0.4305.5; and 2025 GDR to 17.0.1145.4 or CU9 to 17.0.5015.4. Restrict network access to SQL Server and limit authorized accounts until updates are deployed.

fixed in 14.0.2140.2, 14.0.3560.2, 15.0.2200.2, 15.0.4500.2, 16.0.1210.3, 16.0.4305.5, 17.0.5015.4, 17.0.1145.4

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.49%40th percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 20:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-13 20:37Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-qc5v-8339-5w6j
  2. 2026-10-13 20:37Z

this entry in the feed

GET /api/v1/feed/CVE-2026-94512

{
  "etk_id": "ETK-2026-1529",
  "cve_id": "CVE-2026-94512",
  "display_id": "CVE-2026-94512",
  "ghsa_id": "GHSA-qc5v-8339-5w6j",
  "euvd_id": "EUVD-2026-100619",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap buffer overflow in Microsoft SQL Server",
  "summary": "Affected Microsoft SQL Server 2017, 2019, 2022, and 2025 servicing branches contain a heap memory overflow flaw. An authenticated attacker with network access may be able to execute code on the SQL Server host.",
  "mitigation": "Apply the relevant SQL Server security update: update 2017 GDR to 14.0.2140.2 or CU31 to 14.0.3560.2; 2019 GDR to 15.0.2200.2 or CU32 to 15.0.4500.2; 2022 GDR to 16.0.1210.3 or CU27 to 16.0.4305.5; and 2025 GDR to 17.0.1145.4 or CU9 to 17.0.5015.4. Restrict network access to SQL Server and limit authorized accounts until updates are deployed.",
  "vendor": "Microsoft",
  "product": "Microsoft SQL Server 2017 (GDR)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 14.0.0, < 14.0.2140.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "14.0.2140.2"
      ],
      "package_name": "Microsoft SQL Server 2017 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 14.0.3006.16, < 14.0.3560.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "14.0.3560.2"
      ],
      "package_name": "Microsoft SQL Server 2017 for x64-based Systems (CU31)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.0.0, < 15.0.2200.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.0.2200.2"
      ],
      "package_name": "Microsoft SQL Server 2019 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.0.4003.23, < 15.0.4500.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.0.4500.2"
      ],
      "package_name": "Microsoft SQL Server 2019 for x64-based Systems (CU32)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 16.0.0, < 16.0.1210.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "16.0.1210.3"
      ],
      "package_name": "Microsoft SQL Server 2022 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 16.0.4003.1, < 16.0.4305.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "16.0.4305.5"
      ],
      "package_name": "Microsoft SQL Server 2022 for x64-based Systems (CU27)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 17.0.4006.2, < 17.0.5015.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "17.0.5015.4"
      ],
      "package_name": "Microsoft SQL Server 2025 for x64-based Systems (CU9)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 17.0.1050.2, < 17.0.1145.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "17.0.1145.4"
      ],
      "package_name": "Microsoft SQL Server 2025 for x64-based Systems (GDR)",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0049,
  "epss_percentile": 0.4089,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.08024825,
  "t0_at": "2026-10-13T20:37:27.679000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T20:37:27.679000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T20:37:27.679000+00:00",
      "url": "https://github.com/advisories/GHSA-qc5v-8339-5w6j"
    }
  }
}

published 2026-10-14 01:29Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.