{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-121542 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-121542 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-121542 is a low-severity vulnerability in Docker Buildx, published on 3 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-121542 and fix it if it is affected.\n\nWhat it is: CVE-2026-121542 is a low-severity vulnerability in Docker Buildx, published on 3 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-121542 in the wild and no public exploit code.\n\nAffected product: Docker Buildx. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-121542/ (Markdown: https://insights.sbomify.com/CVE-2026-121542/index.md)","id":"CVE-2026-121542","markdown":"https://insights.sbomify.com/CVE-2026-121542/index.md","name":"CVE-2026-121542","record":{"aliases":["DEBIAN-CVE-2026-121542","ECHO-3845-d168-5441","GHSA-rghq-x9hf-hc3r","UBUNTU-CVE-2026-121542"],"analysis":null,"analysis_generated_by":null,"assigner":"Docker","cpe":[],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Bake filesystem path entitlements approval can be skipped for path using basename prefix","id":"CVE-2026-121542","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"smart-sso through 2.0.1 Incorrect Authorization in PermissionFilter Enables Admin Escalation","id":"CVE-2026-121543"},"nickname":null,"packages":[],"prev":{"headline":"Bake filesystem path entitlements approval can be skipped in some multi-target builds","id":"CVE-2026-121541"},"products":["Docker Buildx"],"published":"2026-11-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-04","vendors":["Docker"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-121542/"}