{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-121520 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-121520 is a medium-severity vulnerability in Moby BuildKit, published on 3 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-121520 and fix it if it is affected.\n\nWhat it is: CVE-2026-121520 is a medium-severity vulnerability in Moby BuildKit, published on 3 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-121520 in the wild and no public exploit code.\n\nAffected product: Moby BuildKit. 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-121520/ (Markdown: https://insights.sbomify.com/CVE-2026-121520/index.md)","id":"CVE-2026-121520","markdown":"https://insights.sbomify.com/CVE-2026-121520/index.md","name":"CVE-2026-121520","record":{"aliases":["AZL-112726","AZL-112729","AZL-112756","GHSA-w26x-xg27-7qjc","UBUNTU-CVE-2026-121520"],"analysis":null,"analysis_generated_by":null,"assigner":"Docker","cpe":[],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"}],"description":"In BuildKit versions prior to v0.34.1, a malicious client with access to the BuildKit control APIs can submit a build request that sets an extended attribute on a file outside the BuildKit state directory. Extended attributes in the trusted. or security. namespaces may also be set, potentially giving a program on the host elevated privileges. This issue affects build services that accept build requests from untrusted users. The issue is fixed in v0.34.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":true,"headline":"Malicious client could set xattr value outside of BuildKit state directory","id":"CVE-2026-121520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Possible panic from Git source resolver","id":"CVE-2026-121522"},"nickname":null,"packages":[],"prev":{"headline":"Social Slider Feed \u003c= 2.3.8 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'slidespeed' Parameter","id":"CVE-2026-121519"},"products":["BuildKit"],"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-06","vendors":["Moby"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-121520/"}