# openSUSE-SU-2026:20262-1: Security update for docker-stable

> Enables SELinux by default in Docker to enforce mandatory access controls, mitigating potential container escape risks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Feb 2026

## What is openSUSE-SU-2026:20262-1?

openSUSE-SU-2026:20262-1 is a vulnerability in docker-stable, published on 20 Feb 2026. 

### Official description

This update for docker-stable fixes the following issues:

- Enable SELinux in default daemon.json config (--selinux-enabled).
  This has no practical impact on non-SELinux systems (bsc#1252290).
- Remove git-core recommends on SLE. Most SLE systems have installRecommends=yes
  by default and thus end up installing git with Docker (bsc#1250508).
- Include historical changelog data from before the docker-stable fork.
  This includes CVE numbers for security tracking reasons (bsc#1250596).

## Which versions are affected by openSUSE-SU-2026:20262-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docker-stable` | openSUSE:Leap 16.0 | All versions | 24.0.9_ce-160000.3.1 |

## How do I fix openSUSE-SU-2026:20262-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2026:20262-1 being exploited?

There is no known exploitation of openSUSE-SU-2026:20262-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2026:20262-1 and fix it if it is affected.

What it is: openSUSE-SU-2026:20262-1 is a vulnerability in docker-stable, published on 20 Feb 2026. 
Exploitation: There is no known exploitation of openSUSE-SU-2026:20262-1 in the wild and no public exploit code.

Affected product: docker-stable. 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/openSUSE-SU-2026-20262-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20262-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2026:20262-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2026-20262-1/
Summaries are generated and may contain mistakes; the official description above is the record.