# Buildkit's interactive containers API does not validate entitlements check

Advisory record · `GHSA-wr6v-9f75-vh2g`

- **Identifiers:** `GHSA-wr6v-9f75-vh2g` · `CVE-2024-23653` · `GO-2024-2497`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 31 Jan 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 Jan 2024, 22:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/moby/buildkit` (Go): affected `<0.12.5`; fixed in `0.12.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Buildkit (github.com/moby/buildkit) versions before 0.12.5 are vulnerable. The interactive containers API does not check the security.insecure entitlement, so a party able to use that API can have BuildKit run a container with elevated privileges that should be disallowed. Upgrade to version 0.12.5 or later. Avoid using BuildKit frontends from untrusted sources.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.041, the 91st percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wr6v-9f75-vh2g)

## Sources

- [GitHub Advisory Database: GHSA-wr6v-9f75-vh2g](https://github.com/advisories/GHSA-wr6v-9f75-vh2g)
- [OSV: GHSA-wr6v-9f75-vh2g](https://osv.dev/vulnerability/GHSA-wr6v-9f75-vh2g)
- <https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-23653>
- <https://github.com/moby/buildkit/pull/4602>
- <https://github.com/moby/buildkit/commit/5026d95aa3336e97cfe46e3764f52d08bac7a10e>
- <https://github.com/moby/buildkit/commit/92cc595cfb12891d4b3ae476e067c74250e4b71e>
- <https://github.com/moby/buildkit>
- <https://github.com/moby/buildkit/releases/tag/v0.12.5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wr6v-9f75-vh2g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wr6v-9f75-vh2g/>. Everything for agents: <https://agentprime.io/llms.txt>.
