Live › vulnerability › CVE-2026-121541
In Docker Buildx v0.19.0 through v0.38.0, a Bake definition that builds multiple targets together can expose files on the machine without the expected fs.read approval. An attacker who supplies an untrusted Bake definition can read files the Buildx client can access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 23:15 UTC. All times on this page are UTC.
Teams whose Buildx client runs Bake definitions from sources they do not trust, especially multi-target builds. Teams that only build their own trusted Bake files are at lower risk. The sources do not say whether CI-only or default configurations differ.
No product ranges from the sources yet.
docker buildx version and compare against the affected range v0.19.0 through v0.38.0fs.read entitlements are granted to buildsUnknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition that builds multiple targets together may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, filesystem paths from some targets are not verified against the approved entitlements. Users who run untrusted Bake definitions may be affected. The issue is fixed in v0.38.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-121541")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.