Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ openSUSE-SU-2026:20057-1 — docker (CVE-2025-54388)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for docker

This update for docker fixes the following issues:

Changes in docker:

  • Update to Docker 28.5.1-ce. See upstream changelog online at

<https://docs.docker.com/engine/release-notes/28/#2851>

  • Update to Docker 28.5.0-ce. See upstream changelog online at

<https://docs.docker.com/engine/release-notes/28/#2850>

  • Update to docker-buildx v0.29.0. Upstream changelog:

<https://github.com/docker/buildx/releases/tag/v0.29.0>

  • Remove git-core recommends on SLE. Most SLE systems have

installRecommends=yes by default and thus end up installing git with Docker.

bsc#1250508

This feature is mostly intended for developers ("docker build git://") so

most users already have the dependency installed, and the error when git is

missing is fairly straightforward (so they can easily figure out what they

need to install).

  • Update to docker-buildx v0.28.0. Upstream changelog:

<https://github.com/docker/buildx/releases/tag/v0.28.0>

  • Update to Docker 28.4.0-ce. See upstream changelog online at

<https://docs.docker.com/engine/release-notes/28/#2840>

  • Fixes a nil pointer panic in "docker push". bsc#1248373
  • Update warnings and errors related to "docker buildx ..." so that they

reference our openSUSE docker-buildx packages.

  • Enable building docker-buildx for SLE15 systems with SUSEConnect secret

injection enabled. PED-12534 PED-8905 bsc#1247594

As docker-buildx does not support our SUSEConnect secret injection (and some

users depend "docker build" working transparently), patch the docker CLI so

that "docker build" will no longer automatically call "docker buildx build",

effectively making DOCKER_BUILDKIT=0 the default configuration. Users can

manually use "docker buildx ..." commands or set DOCKER_BUILDKIT=1 in order

to opt-in to using docker-buildx.

Users can silence the "docker build" warning by setting DOCKER_BUILDKIT=0

explicitly.

In order to inject SCC credentials with docker-buildx, users should use

RUN --mount=type=secret,id=SCCcredentials zypper -n ...

in their Dockerfiles, and

docker buildx build --secret id=SCCcredentials,src=/etc/zypp/credentials.d/SCCcredentials,type=file .

when doing their builds.

  • Update to Docker 28.3.3-ce. See upstream changelog online at

<https://docs.docker.com/engine/release-notes/28/#2833>

CVE-2025-54388 bsc#1247367

  • Update to docker-buildx v0.26.1. Upstream changelog:

<https://github.com/docker/buildx/releases/tag/v0.26.1>

  • Update to docker-buildx v0.26.0. Upstream changelog:

<https://github.com/docker/buildx/releases/tag/v0.26.0>

Affected software

openSUSE-SU-2026:20057-1 is recorded against 1 package.

  • docker (fixed in 28.5.1_ce-160000.4.1)

Timeline and source

Published on 17 January 2026 and last revised on 23 March 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-01-17
Updated 2026-08-20
Modified 2026-03-23
Fix URL N/A

Affected Packages

Software From version Fixed in
docker 28.5.1_ce-160000.4.1

Free Vulnerability Check

Is your site affected by openSUSE-SU-2026:20057-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2026:20057-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.