Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

BuildKit interactive containers API does not validate entitlements check

CVSS 3.1 9.8 CRITICALEUVD CVSS 3.1 9.8 CVSS 3.1 · [email protected] · Secondary 9.8 CRITICALCVSS 3.1 · [email protected] · Primary 9.8 CRITICALCVSS_V3 Publisher rating CRITICALFixed by github.com/moby/buildkit 0.12.5osv · severity unknownFixed by github.com/moby/buildkit 0.12.5KEV status unknown

cve-program · CVE-2024-23653

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-0453

Published

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.

Read the publisher's advisory

nvd · CVE-2024-23653

Published

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.

Read the publisher's advisory

osv · GHSA-wr6v-9f75-vh2g

Published

### Impact 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. ### Patches The issue has been fixed in v0.12.5 . ### Workarounds Avoid using BuildKit frontends from untrusted sources. A frontend image is usually specified as the `#syntax` line on your Dockerfile, or with `--frontend` flag when using `buildctl build` command. ### References

Read the publisher's advisory

osv · GO-2024-2497

Published

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

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-23653

Published

BuildKit interactive containers API does not validate entitlements check

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.

Source published
31 Jan 2024 22:03:56 UTC
Source modified
23 Aug 2024 18:16:30 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2024-0453

Published

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…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jan 31, 2024, 10:03:56 PM

dateUpdated: Aug 23, 2024, 6:16:30 PM

19 related source bulletins · separate from aliases

SUSE-SU-2025:20056-1: Security update for docker

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-41110

SUSE-SU-2025:03545-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

WID-SEC-W-2024-3377: Dell PowerProtect Data Domain: Mehrere Schwachstellen

CVE-2024-45759 · CVE-2024-48010 · CVE-2024-48011 · CVE-2017-16829 · CVE-2017-5849 · CVE-2018-7208 · CVE-2019-14889 · CVE-2020-12912 · CVE-2020-16135 · CVE-2020-1730 · CVE-2020-24455 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-27219 · CVE-2021-3565 · CVE-2021-3634 · CVE-2022-1210 · CVE-2022-1622 · CVE-2022-1996 · CVE-2022-22576 · CVE-2022-25313 · CVE-2022-27774 · CVE-2022-27775 · CVE-2022-27776 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-29361 · CVE-2022-32205 · CVE-2022-32206 · CVE-2022-32207 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-35252 · CVE-2022-40023 · CVE-2022-40090 · CVE-2022-42915 · CVE-2022-42916 · CVE-2022-43551 · CVE-2022-43552 · CVE-2022-4603 · CVE-2022-48064 · CVE-2022-48624 · CVE-2023-0461 · CVE-2023-1667 · CVE-2023-1916 · CVE-2023-20592 · CVE-2023-2137 · CVE-2023-22745 · CVE-2023-2283 · CVE-2023-23914 · CVE-2023-23915 · CVE-2023-23916 · CVE-2023-23934 · CVE-2023-25577 · CVE-2023-26965 · CVE-2023-27043 · CVE-2023-2731 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-31083 · CVE-2023-34055 · CVE-2023-35116 · CVE-2023-38286 · CVE-2023-38469 · CVE-2023-38471 · CVE-2023-38472 · CVE-2023-38545 · CVE-2023-38546 · CVE-2023-39197 · CVE-2023-39198 · CVE-2023-39804 · CVE-2023-40217 · CVE-2023-42465 · CVE-2023-4255 · CVE-2023-45139 · CVE-2023-45322 · CVE-2023-45863 · CVE-2023-45871 · CVE-2023-46136 · CVE-2023-46218 · CVE-2023-46219 · CVE-2023-46751 · CVE-2023-48795 · CVE-2023-49083 · CVE-2023-50447 · CVE-2023-5049 · CVE-2023-50495 · CVE-2023-50782 · CVE-2023-51257 · CVE-2023-52425 · CVE-2023-52426 · CVE-2023-5678 · CVE-2023-5717 · CVE-2023-5752 · CVE-2023-6004 · CVE-2023-6597 · CVE-2023-6918 · CVE-2023-7207 · CVE-2024-0450 · CVE-2024-0727 · CVE-2024-0985 · CVE-2024-21626 · CVE-2024-22195 · CVE-2024-22365 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-23672 · CVE-2024-24549 · CVE-2024-25062 · CVE-2024-26130 · CVE-2024-26458 · CVE-2024-26461 · CVE-2024-28085 · CVE-2024-28182 · CVE-2024-28219 · CVE-2024-28757

SUSE-SU-2024:0587-1: Security update for docker

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

SUSE-SU-2025:03540-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

WID-SEC-W-2024-0272: docker: Mehrere Schwachstellen

CVE-2024-21626 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-23650 · CVE-2024-24557

SUSE-SU-2024:3120-1: Security update for buildah, docker

CVE-2024-1753 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-24786 · CVE-2024-28180 · CVE-2024-3727 · CVE-2024-41110

SUSE-RU-2024:4391-1: Recommended update for docker-stable

CVE-2024-23653 · CVE-2024-41110

openSUSE-SU-2024:14059-1: singularity-ce-4.1.3-1.1 on GA media

CVE-2022-23538 · CVE-2022-39237 · CVE-2024-21626 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-3727

openSUSE-SU-2024:13688-1: buildkit-0.12.5-2.1 on GA media

CVE-2024-23653

SUSE-SU-2024:0586-1: Security update for docker

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

openSUSE-SU-2024:14571-1: docker-stable-24.0.9_ce-4.1 on GA media

CVE-2024-23653

SUSE-SU-2025:1102-1: Security update for docker, docker-stable

CVE-2024-23650 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

SUSE-SU-2025:0226-1: Security update for docker-stable

CVE-2024-23650 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110

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

CVE-2024-23653

SUSE-SU-2024:0586-2: Security update for docker

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

openSUSE-SU-2024:13689-1: docker-24.0.7_ce-3.1 on GA media

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

SUSE-SU-2025:20107-1: Security update for buildkit

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

SUSE-SU-2024:1469-1: Security update for docker

CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653

Source published
Jan 31, 2024, 10:03:56 PM (timezone not stated)
Source modified
Aug 23, 2024, 6:16:30 PM (timezone not stated)
Saved here
15 Nov 2026 01:49:21 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2024-23653

Published

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…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-863

Original publisher date fields

published: 2024-01-31T22:15:54.600

lastModified: 2026-06-17T07:13:18.853

1 source CPE criteria · context only
  • cpe:2.3:a:mobyproject:buildkit:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
31 Jan 2024 22:15:54 UTC
Source modified
17 Jun 2026 07:13:18 UTC
Saved here
24 Oct 2026 23:17:22 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 · [email protected] · Primary · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

osv · GHSA-wr6v-9f75-vh2g

Published

Buildkit's interactive containers API does not validate entitlements check

### Impact 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. ### Patches The issue has been fixed in v0.12.5 . ### Workarounds Avoid using BuildKit frontends from untrusted sources. A frontend image is usually specified as the `#syntax` line on your Dockerfile, or with `--frontend` flag when using `buildctl build` command. ### References

Source published
31 Jan 2024 22:43:20 UTC
Source modified
10 Sep 2026 03:50:09 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · CRITICAL

osv · GO-2024-2497

Published

Privilege escalation in github.com/moby/buildkit

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

Source published
7 Feb 2024 04:19:28 UTC
Source modified
4 Feb 2026 03:48:49 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current