medium CVSS 6.2 EPSS <0.1%

CVE-2025-36154·Docker vulnerability

IBM Concert 1.0.0 through 2.1.0 stores sensitive information in cleartext during recursive docker builds which could be obtained by a local user.

Severity
medium
Software
Docker
Fixed in
2.2.0
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

From: 1.0.0

Until: 2.2.0

Fixed in: 2.2.0

How to fix this CVE

Docker versions 1.0.0 through 2.1.0 fail to properly isolate sensitive data during recursive builds, allowing local users with system access to retrieve credentials and secrets stored in build contexts. Upgrade Docker to version 2.2.0 or later to prevent unauthorized exposure of sensitive information during the build process. After patching, audit your build pipelines to ensure no credentials were cached in intermediate layers.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Run `docker --version` to display the currently installed Docker version and confirm if it falls within 1.0.0–2.1.0
  2. Execute `docker info | grep -i version` to cross-verify the daemon version running on your system
  3. Check for multi-stage builds in your Dockerfile using `grep -n FROM Dockerfile` to identify recursive build patterns that may have exposed secrets
  4. Verify the patch was applied by confirming `docker --version` now reports 2.2.0 or later

FAQ

What is CVE-2025-36154?

This vulnerability exists in Docker's build process where sensitive information (API keys, passwords, tokens) is stored in plaintext within build artifacts, allowing local system users to extract credentials from the build environment.

Is CVE-2025-36154 being actively exploited?

No, this CVE is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available, though the local access requirement means it poses risk in multi-tenant or compromised environments.

What versions of Docker are affected by CVE-2025-36154?

Docker versions 1.0.0 through 2.1.0 are vulnerable; version 2.2.0 and later contain the fix.

How do I check if my server is vulnerable to CVE-2025-36154?

Run `docker --version` and compare the output against the affected range (1.0.0–2.1.0); if your version is within this range, your system is vulnerable.

Does Defensia detect CVE-2025-36154?

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

Related Docker CVEs

CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
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.
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-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.

References

Track CVEs across your fleet automatically

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

Get started free