Topic starter
19/10/2026 5:39 pm
TL;DR: Truffle Security shows how Docker image layers can preserve secrets long after files are deleted, and how COPY, hardcoded Dockerfile values, and build arguments expose API secrets and private keys even when the final image looks clean. The governance problem is not just leakage, but the false assumption that deletion inside a build equals revocation.
Editorial analysis by NHI Mgmt Group, based on content published by Truffle Security: “How Secrets Leak out of Docker Images”.
Key questions
Q: What breaks when Docker secrets are copied into image layers or environment files?
A: Secrets can persist long after a container is deleted because they may remain in image layers, registries, or build history.
Q: Why do Docker build arguments create more risk for secrets than many teams expect?
A: Build arguments feel temporary, but Docker records them in build metadata and image layers.
Q: How do security teams know whether developer endpoints are leaking NHI secrets?
A: Look for unexpected token use, unusual outbound connections, unexplained browser profile access, and persistence mechanisms on workstations and build runners.
Practitioner guidance
- Map build-secret exposure paths Inventory where credentials enter Docker builds, including COPY ., hardcoded Dockerfile values, and build arguments, then classify each path by whether it leaves recoverable material in layers or history.
- Replace persistent build secrets with isolated stages Move authentication and dependency fetch steps into a dedicated build stage so the final runtime image excludes source files, temporary credentials, and layer history that are not needed to run the application.
- Use BuildKit only when the consumer does not persist the secret Mount credentials for the specific command that needs them, and verify that the application does not write the secret into files such as npmrc or logs that survive into the image.
Bottom line: Docker layer caching can preserve credentials even after the visible file is deleted, so the final image is not proof that a secret is gone.
What's in the full article
Truffle Security's full post covers the operational detail this post intentionally leaves for the source:
- Step-by-step demonstrations of how layer inspection can recover a deleted .env file from a Docker image
- Exact command sequences for extracting secrets from image layers and history using common Docker tooling
- Concrete examples of multi-stage build patterns that keep build-only credentials out of the final image
- BuildKit secret-mount behaviour and the specific failure mode when a command writes the secret back to disk
👉 Read Truffle Security's analysis of how Docker images leak secrets through layers →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/10/2026 5:39 pm
Layer retention is the real secret-zero problem: Docker does not just package applications, it preserves the evidence of how they were built. A secret that exists in an earlier layer, build command, or cached instruction is still an authentic credential event even if the final image looks clean. That means the security boundary is not the container runtime alone but the full build artifact chain, and practitioners need to treat image provenance as part of secret governance.
A few things that frame the scale:
- 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations, according to the State of Secrets Sprawl 2026.
- The blast radius of the Salesloft-Drift OAuth supply chain attack was 10 times greater than earlier incidents in which attackers breached Salesforce directly.
A question worth separating out:
A: BuildKit secrets mount sensitive material only during a build step, while multi-stage builds isolate entire stages and copy only selected outputs into the final image. BuildKit is useful for temporary access, but it can still leak if a command writes the secret into a file that survives. Multi-stage builds provide stronger containment when the secret must never reach the final stage.
👉 Read our full editorial: Docker image layers keep secrets alive after deletion