← back to feed
CVE-2026-116945

CVE-2026-116945

validatedZero produced an exploit or a check.

GHSA-v967-mw9w-99q9 ↗EUVD-2026-122537 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.2150.2; >= 14.0.3006.16, < 14.0.3570.2; >= 15.0.0, < 15.0.2210.4; >= 15.0.4003.23, < 15.0.4510.2; >= 16.0.0, < 16.0.1220.3; >= 16.0.4003.1, < 16.0.4315.2; >= 17.0.4006.0, < 17.0.5045.3; >= 17.0.1050.2, < 17.0.1155.3
fixed in 14.0.2150.2, 14.0.3570.2, 15.0.2210.4, 15.0.4510.2, 16.0.1220.3, 16.0.4315.2, 17.0.5045.3, 17.0.1155.3
CWE-122 Heap-based Buffer Overflow
ETK-2026-4083Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.8cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
+32mTTV
17mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+32magent stopped
0
+10min
+20min
+30min

description

Microsoft SQL Server 2017, 2019, 2022, and 2025 releases in the affected servicing branches contain a heap-based buffer overflow. An unauthenticated attacker able to reach the SQL Server service over a network may execute code on the affected server.

mitigation

Install the applicable SQL Server security update: 14.0.2150.2 or 14.0.3570.2 for 2017, 15.0.2210.4 or 15.0.4510.2 for 2019, 16.0.1220.3 or 16.0.4315.2 for 2022, or 17.0.5045.3 or 17.0.1155.3 for 2025. Until patched, restrict network access to SQL Server to trusted clients.

fixed in 14.0.2150.2, 14.0.3570.2, 15.0.2210.4, 15.0.4510.2, 16.0.1220.3, 16.0.4315.2, 17.0.5045.3, 17.0.1155.3

check
available
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 18:24Z
Δ 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 check: a technique exists and was validated, 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-11-10 18:24Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-116945

this entry in the feed

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

{
  "etk_id": "ETK-2026-4083",
  "cve_id": "CVE-2026-116945",
  "display_id": "CVE-2026-116945",
  "ghsa_id": "GHSA-v967-mw9w-99q9",
  "euvd_id": "EUVD-2026-122537",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap-based buffer overflow in Microsoft SQL Server",
  "summary": "Microsoft SQL Server 2017, 2019, 2022, and 2025 releases in the affected servicing branches contain a heap-based buffer overflow. An unauthenticated attacker able to reach the SQL Server service over a network may execute code on the affected server.",
  "mitigation": "Install the applicable SQL Server security update: 14.0.2150.2 or 14.0.3570.2 for 2017, 15.0.2210.4 or 15.0.4510.2 for 2019, 16.0.1220.3 or 16.0.4315.2 for 2022, or 17.0.5045.3 or 17.0.1155.3 for 2025. Until patched, restrict network access to SQL Server to trusted clients.",
  "vendor": "Microsoft",
  "product": "Microsoft SQL Server 2017 (GDR)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 14.0.0, < 14.0.2150.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "14.0.2150.2"
      ],
      "package_name": "Microsoft SQL Server 2017 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 14.0.3006.16, < 14.0.3570.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "14.0.3570.2"
      ],
      "package_name": "Microsoft SQL Server 2017 for x64-based Systems (CU31)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.0.0, < 15.0.2210.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.0.2210.4"
      ],
      "package_name": "Microsoft SQL Server 2019 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.0.4003.23, < 15.0.4510.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.0.4510.2"
      ],
      "package_name": "Microsoft SQL Server 2019 for x64-based Systems (CU32)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 16.0.0, < 16.0.1220.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "16.0.1220.3"
      ],
      "package_name": "Microsoft SQL Server 2022 (GDR)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 16.0.4003.1, < 16.0.4315.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "16.0.4315.2"
      ],
      "package_name": "Microsoft SQL Server 2022 for x64-based Systems (CU27)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 17.0.4006.0, < 17.0.5045.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "17.0.5045.3"
      ],
      "package_name": "Microsoft SQL Server 2025 CU10",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 17.0.1050.2, < 17.0.1155.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "17.0.1155.3"
      ],
      "package_name": "Microsoft SQL Server 2025 for x64-based Systems (GDR)",
      "purl": null
    }
  ],
  "cwes": [
    122
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 17.45725738333333,
  "t0_at": "2026-11-10T18:24:30.902000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-10T18:56:29.690375+00:00",
      "days": 0.022208198784722223,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T18:24:30.902000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-10T18:24:30.902000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T18:24:30.902000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116945"
    }
  }
}

published 2026-11-10 18:41Z
last change 2026-11-11 00:21Z

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.