SUSE · Security update for docker
Affects SUSESource GCVE Database
Not known to be exploited.
Data as of 15 Nov 2026, 22:50 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
Description
This update for docker fixes the following issues: Update to docker-buildx v0.28.0. See upstream changelog: <https://github.com/docker/buildx/releases/tag/v0.28.0> Update to Docker 28.4.0-ce. See upstream changelog: <https://docs.docker.com/engine/release-notes/28/#2840> - 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.jsc#PED-12534jsc#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> Security issue fixed: - CVE-2025-54388: firewalld reload can make published container ports accessible from remote hosts (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>
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_20743-1.json (opens in a new tab)
- suse.com/support/update/announcement/2025/suse-su-202520743-1/ (opens in a new tab)
- lists.suse.com/pipermail/sle-updates/2025-September/041897.html (opens in a new tab)
- bugzilla.suse.com/1247367 (opens in a new tab)
- bugzilla.suse.com/1247594 (opens in a new tab)
- suse.com/security/cve/CVE-2025-54388/ (opens in a new tab)