Skip to content

Product

ubuntu/docker.io vulnerabilities

75 published CVES affecting ubuntu/docker.io, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
75
Critical
5
High
29
Medium
38
Low
3
Unscored
0
CISA KEV
0

Latest ubuntu/docker.io CVEs

Newest publication first · page 1 of 3

  1. MediumCVSS 6.7 EPSS 0.12%

    In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by that daemon. The issue is fixed in v0.34.2.

  2. MediumCVSS 6.0 EPSS 0.25%

    A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more strict...

  3. MediumCVSS 6.8 EPSS 0.11%

    The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make buildkitd allocate memory proportional to that file, potentially exhausting memory and terminating th...

  4. HighCVSS 7.5 EPSS 0.17%

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKi...

  5. MediumCVSS 5.9 EPSS 0.16%

    An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.