SUSE-SU-2026:3818-1 Security update for docker
Not scored
Published
Check this codebase for SUSE-SU-2026:3818-1 and fix it if it is affected.
What it is: SUSE-SU-2026:3818-1 is a vulnerability in docker, published on 26 Aug 2026.
Exploitation: There is no known exploitation of SUSE-SU-2026:3818-1 in the wild and no public exploit code.
Affected product: docker. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2026-3818-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-3818-1/index.md)
Docker was rebuilt against a newer Go security release, addressing underlying library vulnerabilities in the container runtime.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is SUSE-SU-2026:3818-1?
SUSE-SU-2026:3818-1 is a vulnerability in docker, published on 26 Aug 2026.
Official description
This update for docker rebuilds it against the current go security release.
Which versions are affected by SUSE-SU-2026:3818-1?
Linux distribution packages (15)
docker SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Micro 5.3 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Micro 5.4 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Micro 5.5 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Module for Containers 15 SP7 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 29.4.0_ce-150000.259.1 |
docker SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 29.4.0_ce-150000.259.1 |
How do I fix SUSE-SU-2026:3818-1?
Apply the vendor's patch.
Is SUSE-SU-2026:3818-1 being exploited?
There is no known exploitation of SUSE-SU-2026:3818-1 in the wild and no public exploit code.