Artifact Immutability as a Release Primitive: Content Addressing, Digest Pinning, and the Substitution Attack Surface
Most teams treat image tags as release identifiers. They are not. A tag is a mutable pointer sitting on top of a content-addressed blob store. The digest— sha256:<64-hex> —is the identifier. Conflating the two produces a class of failure that looks like a deployment problem but is actually an artifact provenance problem: the rollback you thought was safe pulled a different image than the one you certified, the canary that passed load testing ran a different binary than production, or an attacker overwrote a tag between your CI scan and your Kubernetes pull.
This article examines what artifact immutability actually means in mechanical terms, where the guarantees break down, and how to enforce them across the CI/CD boundary without slowing rollouts.
What a Digest Guarantees and What It Does Not
An OCI image digest is the SHA-256 hash of the image manifest—not the layers, not the config…