Credential disclosure via unredacted Git URL metadata
Published Mar 6, 2023 · Updated Feb 25, 2025
Information exposure in Moby Project BuildKit 0.10.0 through 0.11.3 allows attackers to read Git credentials from build metadata. The provenance predicate copied userinfo from context and vcs:source Git URLs into attestations or BuildInfo instead of redacting it. Exposure requires credentials embedded in a Git URL or supplied as VCS hints and access to the resulting provenance attestation or BuildInfo.
Summary
What happened
Information exposure in Moby Project BuildKit 0.10.0 through 0.11.3 allows attackers to read Git credentials from build metadata. The provenance predicate copied userinfo from context and vcs:source Git URLs into attestations or BuildInfo instead of redacting it. Exposure requires credentials embedded in a Git URL or supplied as VCS hints and access to the resulting provenance attestation or BuildInfo.
The record
- CVE
- CVE-2023-26054
- Published
- Mar 6, 2023
- Updated
- Feb 25, 2025
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.10.0, < 0.11.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo