CVE-2026-93316

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

GHSA-r456-g3gm-cvxf ↗EUVD-2026-92527 ↗

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.
docker BuildKit <= v0.33.0
fixed in >= v0.33.1
ETK-2026-184, permanent identifier
15d 18h 52msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −5.0dcve.org publicationwaiting for further signals+0.0d
−4d
−3d
−2d
−1d

description

docker BuildKit may panic while processing builds that use CDI devices when the daemon has been started with --cdi-disabled. This can cause a denial of service when a build uses CDI devices; the affected configuration requires that startup flag or the corresponding TOML setting.

mitigation

Upgrade docker to >= v0.33.1 or later.

fixed in >= v0.33.1

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.24%13th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 17:42Z
Δ 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-09-30 18:51Z
  2. 2026-10-05 17:42Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-184",
  "cve_id": "CVE-2026-93316",
  "display_id": "CVE-2026-93316",
  "ghsa_id": "GHSA-r456-g3gm-cvxf",
  "euvd_id": "EUVD-2026-92527",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Daemon panic in docker BuildKit CDI device handling",
  "summary": "docker BuildKit may panic while processing builds that use CDI devices when the daemon has been started with `--cdi-disabled`. This can cause a denial of service when a build uses CDI devices; the affected configuration requires that startup flag or the corresponding TOML setting.",
  "mitigation": "Upgrade docker to >= v0.33.1 or later.",
  "vendor": "docker",
  "product": "BuildKit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= v0.33.0"
      ],
      "ecosystem": "docker",
      "fixed_versions": [
        ">= v0.33.1"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0024,
  "epss_percentile": 0.1347,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.67959545,
  "t0_at": "2026-10-05T17:42:12.969000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T18:51:40+00:00",
      "days": -4.951770474537037,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T17:42:12.969000+00:00",
      "url": "https://github.com/moby/buildkit/security/advisories/GHSA-r456-g3gm-cvxf"
    }
  }
}

published 2026-10-01 01:30Z
last change 2026-10-21 12:26Z

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.