← back to feed
CVE-2026-88243

CVE-2026-88243

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

GHSA-fr3f-5mwq-3j7w ↗EUVD-2026-121733 ↗

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 Windows Server 2016 >= 10.0.14393.0, < 10.0.14393.9688; >= 10.0.17763.0, < 10.0.17763.9487; >= 10.0.20348.0, < 10.0.20348.5870; >= 10.0.26100.0, < 10.0.26100.33822
fixed in 10.0.14393.9688, 10.0.17763.9487, 10.0.20348.5870, 10.0.26100.33822
ETK-2026-4104Zero'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
8h 18msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h10m
0
+2h
+6h
+8h
+10h
+12h

description

Microsoft Windows Server 2016 systems running Windows DHCP Server are affected by an out-of-bounds read. An unauthorized attacker with network access to the DHCP Server service may be able to execute code remotely.

mitigation

Restrict network access to the Windows DHCP Server service to trusted hosts and networks. Apply vendor remediation when a supported update is identified.

fixed in 10.0.14393.9688, 10.0.17763.9487, 10.0.20348.5870, 10.0.26100.33822

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 18:16Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-10 18:16Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-fr3f-5mwq-3j7w
  2. 2026-11-10 18:16Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4104",
  "cve_id": "CVE-2026-88243",
  "display_id": "CVE-2026-88243",
  "ghsa_id": "GHSA-fr3f-5mwq-3j7w",
  "euvd_id": "EUVD-2026-121733",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in Windows DHCP Server",
  "summary": "Microsoft Windows Server 2016 systems running Windows DHCP Server are affected by an out-of-bounds read. An unauthorized attacker with network access to the DHCP Server service may be able to execute code remotely.",
  "mitigation": "Restrict network access to the Windows DHCP Server service to trusted hosts and networks. Apply vendor remediation when a supported update is identified.",
  "vendor": "Microsoft",
  "product": "Windows Server 2016",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.14393.0, < 10.0.14393.9688"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.14393.9688"
      ],
      "package_name": "Windows Server 2016",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.14393.0, < 10.0.14393.9688"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.14393.9688"
      ],
      "package_name": "Windows Server 2016 (Server Core installation)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.17763.0, < 10.0.17763.9487"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.17763.9487"
      ],
      "package_name": "Windows Server 2019",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.17763.0, < 10.0.17763.9487"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.17763.9487"
      ],
      "package_name": "Windows Server 2019 (Server Core installation)",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.20348.0, < 10.0.20348.5870"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.20348.5870"
      ],
      "package_name": "Windows Server 2022",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.26100.0, < 10.0.26100.33822"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.26100.33822"
      ],
      "package_name": "Windows Server 2025",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.26100.0, < 10.0.26100.33822"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.0.26100.33822"
      ],
      "package_name": "Windows Server 2025 (Server Core installation)",
      "purl": null
    }
  ],
  "cwes": null,
  "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.272621533333332,
  "t0_at": "2026-11-10T18:16:59.675000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T18:16:59.675000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T18:16:59.675000+00:00",
      "url": "https://github.com/advisories/GHSA-fr3f-5mwq-3j7w"
    }
  }
}

published 2026-11-10 22:10Z
last change 2026-11-11 06:19Z

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.