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 28 Jul 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 Go 1.24 for builds, to match upstream. - Update to Docker 28.3.2-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/28/#2832> - Update to Docker 28.3.1-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/28/#2831> - Update to Docker 28.3.0-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/28/#2830> bsc#1246556 - Update to docker-buildx v0.25.0. Upstream changelog: <https://github.com/docker/buildx/releases/tag/v0.25.0> - CVE-2025-22872: golang.org/x/net/html: Fixed incorrectly interpreted tags causing content to be placed wrong scope during DOM construction (bsc#1241830) - Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as Docker does not have permission to access the host zypper credentials in this mode (and unprivileged users cannot disable the feature using /etc/docker/suse-secrets-enable.) bsc#1240150 - Always clear SUSEConnect suse_* secrets when starting containers regardless of whether the daemon was built with SUSEConnect support. Not doing this causes containers from SUSEConnect-enabled daemons to fail to start when running with SUSEConnect-disabled (i.e. upstream) daemons. This was a long-standing issue with our secrets support but until recently this would've required migrating from SLE packages to openSUSE packages (which wasn't supported). However, as SLE Micro 6.x and SLES 16 will move away from in-built SUSEConnect support, this is now a practical issue users will run into. bsc#1244035
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_20510-1.json (opens in a new tab)
- suse.com/support/update/announcement/2025/suse-su-202520510-1/ (opens in a new tab)
- lists.suse.com/pipermail/sle-updates/2025-August/041041.html (opens in a new tab)
- bugzilla.suse.com/1240150 (opens in a new tab)
- bugzilla.suse.com/1241830 (opens in a new tab)
- bugzilla.suse.com/1242114 (opens in a new tab)
- bugzilla.suse.com/1243833 (opens in a new tab)
- bugzilla.suse.com/1244035 (opens in a new tab)
- bugzilla.suse.com/1246556 (opens in a new tab)
- suse.com/security/cve/CVE-2025-22872/ (opens in a new tab)