Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-23653: BuildKit interactive containers API does not validate entitlements check

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.4% (FIRST EPSS); higher than 88.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: github.com/moby/buildkit (Go) 0.12.5; docker-stable (openSUSE:Leap 15.5) 24.0.9_ce-150000.1.8.1; docker-stable (openSUSE:Leap 15.6) 24.0.9_ce-150000.1.11.1.

Add it to your regular patch cycle. Upgrade to github.com/moby/buildkit (Go) 0.12.5; docker-stable (openSUSE:Leap 15.5) 24.0.9_ce-150000.1.8.1; docker-stable (openSUSE:Leap 15.6) 24.0.9_ce-150000.1.11.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available
Published
Jan 31, 2024
Updated
Jun 17, 2026
EPSS
3.4% · 88th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · GitHub_M
9.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-23653

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for mobyproject records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
mobyprojectbuildkit

Using buildkit? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for buildkit

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mobyproject buildkitbefore 0.12.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • moby buildkit

    • < 0.12.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/moby/buildkitbefore 0.12.50.12.5
openSUSE:Leap 15.5docker-stablebefore 24.0.9_ce-150000.1.8.124.0.9_ce-150000.1.8.1
openSUSE:Leap 15.6docker-stablebefore 24.0.9_ce-150000.1.11.124.0.9_ce-150000.1.11.1
openSUSE:Leap Micro 5.3dockerbefore 24.0.7_ce-150000.193.124.0.7_ce-150000.193.1
openSUSE:Leap Micro 5.5dockerbefore 25.0.6_ce-150000.207.125.0.6_ce-150000.207.1
openSUSE:Tumbleweedbuildkitbefore 0.12.5-2.10.12.5-2.1
openSUSE:Tumbleweeddockerbefore 24.0.7_ce-3.124.0.7_ce-3.1
openSUSE:Tumbleweeddocker-stablebefore 24.0.9_ce-4.124.0.9_ce-4.1
openSUSE:Tumbleweedsingularity-cebefore 4.1.3-1.14.1.3-1.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSbuildahbefore 1.35.4-150300.8.25.11.35.4-150300.8.25.1
SUSE:Linux Enterprise Micro 5.3dockerbefore 25.0.6_ce-150000.207.125.0.6_ce-150000.207.1
SUSE:Linux Enterprise Micro 5.3dockerbefore 24.0.7_ce-150000.193.124.0.7_ce-150000.193.1
SUSE:Linux Enterprise Module for Containers 12dockerbefore 24.0.7_ce-98.106.124.0.7_ce-98.106.1
SUSE:Linux Enterprise Module for Containers 12dockerbefore 25.0.5_ce-98.112.125.0.5_ce-98.112.1
SUSE:Linux Enterprise Module for Containers 15 SP5docker-stablebefore 24.0.9_ce-150000.1.8.124.0.9_ce-150000.1.8.1
SUSE:Linux Enterprise Module for Containers 15 SP6docker-stablebefore 24.0.9_ce-150000.1.11.124.0.9_ce-150000.1.11.1
SUSE:Linux Enterprise Server 12 SP5-LTSSdockerbefore 27.5.1_ce-98.126.127.5.1_ce-98.126.1
SUSE:Linux Enterprise Server 12 SP5-LTSSdocker-stablebefore 24.0.9_ce-1.11.124.0.9_ce-1.11.1
SUSE:Linux Micro 6.0buildkitbefore 0.12.5-1.10.12.5-1.1
SUSE:Linux Micro 6.0dockerbefore 25.0.6_ce-1.125.0.6_ce-1.1

Same product

mobyproject: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-33747BuildKit vulnerable to malicious frontend causing file escape outside of storage root
    39Monitor
  • CVE-2024-23652BuildKit possible host system access from mount stub cleaner
    37Monitor
  • CVE-2026-33748BuildKit Git URL subdir component can cause access to restricted files
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-23650Jan 31, 2024 · BuildKit possible panic when incorrect parameters sent from frontend
    21Monitor
  • ← EarlierCVE-2024-23651Jan 31, 2024 · BuildKit possible race condition with accessing subpaths from cache mounts
    29Monitor
  • Later →CVE-2026-15788Jul 20, 2026 · WCOW cache mount source selector resolves NTFS junctions outside of cache root
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/moby/buildkit0.12.5Package registry (OSV)
opensuse:buildkit0.12.5-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:docker24.0.7_ce-150000.193.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:docker-stable24.0.9_ce-150000.1.8.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:singularity-ce4.1.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:buildah1.35.4-150300.8.25.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:buildkit0.12.5-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:docker24.0.7_ce-150000.193.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:docker-stable24.0.9_ce-150000.1.8.1 · SUSE:Linux Enterprise Module for Containers 15 SP5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:52024-12-13

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+316 d
  3. TodayOct 30, 2026+1003 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records