All issues

Runtime Evidence · No. 01

containerd crash bugs and Istio auth bypass

2026-10-20

The lead

containerd: containerd: daemon crash when processing an image manifest with a malformed digest (CVE-2026-95839)

containerd crashes on an image manifest with a malformed digest plus the subject annotation, reachable via default CRI PullImage. Patch containerd and avoid pulling untrusted images until then.

github.com/containerd

Also this week

Our take: CVSS is a severity, not a work order

CVSS says how bad a CVE is if it can be exploited. It doesn't know whether the vulnerable code ever ran in your cluster.

  1. Installed

    in the image

  2. Loaded

    mapped into a process

  3. Executed

    the vulnerable path ran

A scanner sees the first box. Exposure lives in the last one.

Is the vulnerable library even mapped into the running process?

Shell
kubectl exec <pod> -- \
  cat /proc/1/maps \
  | awk '{print $6}' \
  | grep '\.so' | sort -u

Not in the list: PID 1 isn't using it right now. Not proof of safety, but a better first question than the score.

Read the full article

Why CVSS Scores Fail Platform Teams and What Runtime Reachability Fixes

Weekly email

Runtime Evidence

One email a week: a runtime finding worth understanding, how it was investigated, and what to check in your own clusters. No product pitches in disguise; unsubscribe in one click.