# CVE-2026-103433: Bake filesystem entitlement consent is skipped for certain secret and oci-layout definitions

> Attackers can read local files or access OCI layouts by bypassing filesystem entitlement checks in Docker Buildx Bake definitions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** BELL-CVE-2026-103433, DEBIAN-CVE-2026-103433, ECHO-649c-d979-2cbe, GHSA-p54p-jq4x-rc28, UBUNTU-CVE-2026-103433

## What is CVE-2026-103433?

CVE-2026-103433 is a medium-severity missing authorization vulnerability in Docker Buildx, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Docker Buildx Bake does not request the expected fs.read approval for certain filesystem inputs. An untrusted Bake definition can expose a readable file through a pathless secret whose ID is interpreted as a client-side pathname, or consume a local OCI image layout outside the project after entitlement validation checks a different path representation. Users who run untrusted Bake definitions are affected.

Weakness: CWE-862 (Missing Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-103433 being exploited?

There is no known exploitation of CVE-2026-103433 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103433 and fix it if it is affected.

What it is: CVE-2026-103433 is a medium-severity missing authorization vulnerability in Docker Buildx, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-103433 in the wild and no public exploit code.

Affected product: Docker Buildx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103433/ (Markdown: https://insights.sbomify.com/CVE-2026-103433/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103433
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103433
- OSV: https://osv.dev/vulnerability/CVE-2026-103433

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103433/
Summaries are generated and may contain mistakes; the official description above is the record.