{"answers":{"affected":"2 open source packages ship an affected version, including github.com/moby/buildkit. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26054 in the wild and no public exploit code.","fix":"Upgrade github.com/moby/buildkit to 0.11.4 or later.","what":"CVE-2023-26054 is a medium-severity vulnerability in moby buildkit, published on 6 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-26054 and fix it if it is affected.\n\nWhat it is: CVE-2023-26054 is a medium-severity vulnerability in moby buildkit, published on 6 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-26054 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/moby/buildkit (Go): affected from 0.10.0; fixed in 0.11.4\n- github.com/moby/buildkit (Go): affected from 0.10.0; fixed in 0.11.4\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-26054/ (Markdown: https://insights.sbomify.com/CVE-2023-26054/index.md)","id":"CVE-2023-26054","markdown":"https://insights.sbomify.com/CVE-2023-26054/index.md","name":"CVE-2023-26054","record":{"aliases":["CLEANSTART-2026-GE40868","GHSA-gc89-7gcr-jxqc"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"BuildKit build toolkit","requires_auth":"none","summary":"Attackers with access to build provenance attestations can view credentials embedded in Git URLs used during the build process.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"buildkit","vendor":"mobyproject"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In affected versions when the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation. Git URL can be passed in two ways: 1) Invoking build directly from a URL with credentials. 2) If the client sends additional version control system (VCS) info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from `.git/config` file. When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation. Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable. In v0.10, when building directly from Git URL, the same URL could be visible in `BuildInfo` structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable. This bug has been fixed in v0.11.4. Users are advised to upgrade. Users unable to upgrade may disable VCS info hints by setting `BUILDX_GIT_INFO=0`. `buildctl` does not set VCS hints based on `.git` directory, and values would need to be passed manually with `--opt`.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Credentials inlined to Git URLs could end up in provenance attestation in BuildKit","id":"CVE-2023-26054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":5,"next":{"headline":"XWiki Commons may allow privilege escalation to programming rights via user's first name","id":"CVE-2023-26055"},"packages":[{"ecosystem":"Go","fixed":["0.11.4"],"introduced":["0.10.0"],"last_affected":[],"package":"github.com/moby/buildkit","purl":null,"source":"GHSA-gc89-7gcr-jxqc"},{"ecosystem":"Go","fixed":["0.11.4"],"introduced":["0.10.0"],"last_affected":[],"package":"github.com/moby/buildkit","purl":"pkg:golang/github.com/moby/buildkit","source":"GHSA-gc89-7gcr-jxqc"}],"prev":{"headline":"Gradle usage of long IDs for PGP keys opens potential for collision attacks","id":"CVE-2023-26053"},"products":["buildkit"],"published":"2023-03-06","related":[{"cvss_score":10,"headline":"BuildKit possible host system access from mount stub cleaner","id":"CVE-2024-23652","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":9.8,"headline":"BuildKit interactive containers API does not validate entitlements check","id":"CVE-2024-23653","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":8.7,"headline":"BuildKit possible race condition with accessing subpaths from cache mounts","id":"CVE-2024-23651","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":8.4,"headline":"BuildKit vulnerable to malicious frontend causing file escape outside of storage root","id":"CVE-2026-33747","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":8.2,"headline":"BuildKit Git URL subdir component can cause access to restricted files","id":"CVE-2026-33748","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":6.9,"headline":"Malicious client can bypass destination directory validation on local sources upload","id":"CVE-2026-15789","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":6.5,"headline":"Git source checkout from a bundle file could lead to command injection","id":"CVE-2026-15793","kev_date_added":null,"published":"2026-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-25","vendors":["moby"]},"summary":"Attackers with access to build provenance attestations can view credentials embedded in Git URLs used during the build process.","url":"https://insights.sbomify.com/CVE-2023-26054/"}