Live › vulnerability › CVE-2026-121542
Docker Buildx v0.19.0 through v0.38.0 can let an untrusted Bake definition read files that should need fs.read approval. The check is skipped for paths beside the working directory whose names start with the working directory's basename.
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 that run Docker Buildx Bake definitions they did not write or do not trust. Exploitation needs matching filenames next to the current project directory, so routine builds of your own projects are less exposed.
No product ranges from the sources yet.
docker buildx version and check whether the version is between v0.19.0 and v0.38.0.docker buildx bake.Unknown 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 may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, paths under the same parent directory as the current working directory whose names use the working directory's basename as a prefix can skip the filesystem entitlement check. Exploitation requires specific matching filenames next to the current project directory. 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-121542")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.