Skip to main content
CVE-2026-93316VulnerabilityPublished

Microsoft · Starting daemon with --cdi-disabled flag can lead to panic on specific builds

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-93316· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 0.33.1 soon.

Data as of 17 Nov 2026, 10:22 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.33.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade BuildKit and moby/buildkit to 0.33.1.

Affected software

ProductAffectedFixed in
mobyBuildKitAffected
  • <0.33.1
Fixed in
  • 0.33.1
GitHubmoby/buildkitpkg:github/moby/buildkitOther threatsAffected
  • <0.33.1
Fixed in
  • 0.33.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Starting the daemon with the --cdi-disabled flag on Microsoft product version 4.0 can cause a panic on specific builds. This vulnerability is identified as CVE-2026-93316 and relates to a null pointer dereference (CWE-476). No CVSS score or detailed impact information is provided.

References

Community reviews

Loading reviews…