Skip to content
Fencer Vulns
medium 6.5

CVE-2023-26054 json

Credentials inlined to Git URLs could end up in provenance attestation in BuildKit

published 2023-03-06 3 y ago modified 2026-06-17 4 mo ago also GHSA-gc89-7gcr-jxqc , EUVD-2023-1011

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/moby/buildkit 0.11.4
  • mobyproject buildkit 0.11.4
  • docker Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 23.0.2-r0

alpine advisories ALPINE-CVE-2023-26054

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-26054 updated cvss 6.5

buildkit: Data disclosure in provenance attestation describing a build

  • Red Hat OpenShift Container Platform 4.13 openshift4/ose-docker-builder v4.13.0-202306050632.p0.gd02643e.assembly.stream
    fixed: vendor fix RHSA-2023:3537
  • Red Hat RHOSSM 2.4 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.4.4-5, openshift-service-mesh/kiali-rhel8 1.65.9-4, openshift-service-mesh/grafana-rhel8 2.4.4-2, openshift-service-mesh/proxyv2-rhel8 2.4.4-5, openshift-service-mesh/istio-cni-rhel8 2.4.4-5, openshift-service-mesh/ratelimit-rhel8 2.4.4-2, +3 more
    fixed: vendor fix RHSA-2023:5952
  • Red Hat OpenShift Serverless openshift-serverless-1/client-kn-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-tools-rhel9, openshift4/oc-mirror-plugin-rhel9 Red Hat OpenShift Container Platform 4.13 openshift4/ose-cli v4.13.0-202305312300.p0.g05d83ef.assembly.stream, openshift4/ose-pod v4.13.0-202305312300.p0.g7a891f0.assembly.stream, openshift4/ose-tests v4.13.0-202306051456.p0.gf210c2d.assembly.stream, openshift4/ose-console v4.13.0-202306061716.p0.g9222e2a.assembly.stream, openshift4/ose-deployer v4.13.0-202305312300.p0.g05d83ef.assembly.stream, openshift4/ose-hyperkube v4.13.0-202305312300.p0.g7a891f0.assembly.stream, +43 more Red Hat Quay 3 quay/quay-builder-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
20 mo ago

Exploit prediction

1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/moby/buildkit
>=0.10.0, <0.11.4
0.11.4

Affected products

  • moby buildkit

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.