CVE-2026-93318

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

GHSA-f2v9-hprr-32q3 ↗EUVD-2026-92532 ↗

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
CWE-354 Improper Validation of Integrity Check Value
ETK-2026-174, permanent identifier
15d 14h 48msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dcve.org publication+5.0dwaiting for further signals
0
+1d
+2d
+3d
+4d

description

Docker BuildKit may associate image-layer cache or snapshot state with attacker-controlled content based on inconsistent layer metadata. If an untrusted image is processed by a BuildKit daemon with shared or persistent cache before a trusted build, attacker-supplied code may execute during the later build and access build resources or alter outputs.

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.
–
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.
0.17%5th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 17:45Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-09-30 18:53Z
  2. 2026-10-05 17:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-174",
  "cve_id": "CVE-2026-93318",
  "display_id": "CVE-2026-93318",
  "ghsa_id": "GHSA-f2v9-hprr-32q3",
  "euvd_id": "EUVD-2026-92532",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Image layer identity confusion in Docker BuildKit",
  "summary": "Docker BuildKit may associate image-layer cache or snapshot state with attacker-controlled content based on inconsistent layer metadata. If an untrusted image is processed by a BuildKit daemon with shared or persistent cache before a trusted build, attacker-supplied code may execute during the later build and access build resources or alter outputs.",
  "mitigation": "Upgrade docker to >= v0.33.1 or later.",
  "vendor": "docker",
  "product": "Docker BuildKit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= v0.33.0"
      ],
      "ecosystem": "docker",
      "fixed_versions": [
        ">= v0.33.1"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    354
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0017,
  "epss_percentile": 0.056,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.287309283333332,
  "t0_at": "2026-10-05T17:45:39.491000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T18:53:39+00:00",
      "days": -4.952783460648148,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T17:45:39.491000+00:00",
      "url": "https://github.com/moby/buildkit/security/advisories/GHSA-f2v9-hprr-32q3"
    }
  }
}

Anchor corroborated by the cve.org commit 2a885e8da96a.

published 2026-10-01 00:13Z
last change 2026-10-21 04:45Z

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.