medium CVSS 6.5

CVE-2026-24845·Docker vulnerability

malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 0.10.0 and prior to version 1.20.3, malcontent could be made to expose Docker registry credentials if it scanned a specially crafted OCI image reference. malcontent uses google/go-containerregistry for OCI image pulls, which by default uses the Docker credential keychain. A malicious registry could return a `WWW-Authenticate` header redirecting token authentication to an attacker-controlled endpoint, causing credentials to be sent to that endpoint. Version 1.20.3 fixes the issue by defaulting to anonymous auth for OCI pulls.

Severity
medium
Software
Docker
Fixed in
1.20.3
Published
2026-01-29

Affected versions

From: 0.1.0

Until: 1.20.3

Fixed in: 1.20.3

How to fix this CVE

Update Docker to version 1.20.3 or later to remediate the credential exposure vulnerability in the OCI image scanning process. The vulnerability allows malicious registries to intercept Docker credentials through manipulated authentication headers. After updating, verify the new version is running and restart any dependent services that rely on Docker authentication.

sudo dnf update docker-ce --assumeyes

Defensia detects this vulnerability

How to check if you are affected

  1. Run 'docker --version' and verify the installed version is below 1.20.3; affected versions range from 0.10.0 to 1.20.2
  2. Check if OCI image scanning or malcontent is enabled in your Docker environment with 'docker ps -a | grep malcontent'
  3. Search system logs for failed or unexpected authentication attempts to external registries: 'grep -i "authentication\|registry" /var/log/docker.log | head -20'
  4. After patching, confirm the new version with 'docker --version' and verify no lingering credentials are cached in ~/.docker/config.json

FAQ

What is CVE-2026-24845?

This vulnerability allows malicious OCI image registries to redirect Docker credential authentication requests to attacker-controlled servers, potentially exposing stored registry credentials. The flaw exists in how Docker handles WWW-Authenticate header redirects during image pulls.

Is CVE-2026-24845 being actively exploited?

No, this vulnerability is not currently listed on the CISA KEV catalog and no public exploits are available, but the medium severity (CVSS 6.5) and credential exposure risk warrant prompt patching.

What versions of Docker are affected by CVE-2026-24845?

Docker versions 0.10.0 through 1.20.2 are vulnerable; version 1.20.3 and later include the fix.

How do I check if my server is vulnerable to CVE-2026-24845?

Run 'docker --version' and compare the output to 1.20.3; if your version is lower, you are affected. You can also check 'docker inspect' on running containers to identify if OCI image scanning is in use.

Does Defensia detect CVE-2026-24845?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-24845 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-44181CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.
CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-44182CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-24845. Free for 1 server.

Get started free