Most teams discover a critical CVE in a container image the same way: a scanner running against the production cluster fires an alert at 3pm on a Friday, and someone has to figure out whether the vulnerable library is actually reachable, who owns the base image, and how fast a patched version can be shipped. That workflow is expensive and stressful. The fix is unglamorous: move the detection left, into the pull request, where the cost of a change is a one-line bump in a lockfile instead of an emergency change request.
This article shows how to build that guardrail with two small, focused tools β Syft to produce a CycloneDX SBOM , and Grype to scan it β wired into GitHub Actions , with a severity policy that fails the build and an exception mechanism that is documented, time-boxed, and reviewable.β¦