Dockerfile Source Not Pinned

LOW

FROM instruction without digest pinning. Consider using @sha256:... for immutable builds.

Rule Information

Language
Docker
Category
Audit
Author
Shivasurya
Shivasurya
Last Updated
2026-03-22
Tags
dockerdockerfilefromdigestsha256immutabilitysupply-chainreproducibilityauditsecurity
CWE References

Interactive Playground

Experiment with the vulnerable code and security rule below. Edit the code to see how the rule detects different vulnerability patterns.

pathfinder scan --ruleset docker/DOCKER-AUD-001 --project .
1
2
3
4
5
6
7
rule.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

About This Rule

Understanding the vulnerability and how it is detected

Detects FROM instructions without digest pinning (@sha256:...). Tags are mutable and can be updated to point to different images, while digests are immutable references to specific image layers.

How to Fix

Recommended remediation steps

  • 1Review your Dockerfile to address the dockerfile source not pinned issue
  • 2Follow Docker official best practices for image building
  • 3Use docker build --check to validate Dockerfile syntax and best practices

References

External resources and documentation

Similar Rules

Explore related security rules for Docker

Frequently Asked Questions

Common questions about Dockerfile Source Not Pinned

FROM instruction without digest pinning. Consider using @sha256:... for immutable builds.
Review the secure code example in the playground above and apply the recommended pattern to your Dockerfile or docker-compose.yml.

New feature

Get these findings posted directly on your GitHub pull requests

The Dockerfile Source Not Pinned rule runs in CI and posts inline review comments on the exact lines — no dashboard, no SARIF viewer.

See how it works