Release v4.7.4 · liamromanis101/K8s-container_escape_audit
Liam R. — Freelance Penetration Tester
v4.7.4 — containerd CRI-plugin cluster + CrackArmor
v4.7.4 closes two container-escape coverage gaps found while reviewing advisories published since the last sweep. The CVE database grows from 32 to 38 entries; the check count stays at 53.
containerd CRI-plugin cluster (AWS bulletin 2026-046)
Five CVEs in the containerd CRI plugin, affecting 1.7 through 2.3, fixed in 2.3.2 / 2.2.5 / 2.1.9 / 2.0.10 / 1.7.33:
CVE-2026-50195 (8.8) — checkpoint-import image-cache poisoning → cross-pod code execution on shared nodes
CVE-2026-53488 (8.3) — image LABEL propagated unsanitised → host command execution (no checkpoint/restore required)
CVE-2026-53492 (6.8) — CDI annotation smuggling → device / host-mount injection
CVE-2026-53489 — checkpoint-restore symlink → arbitrary host file read
CVE-2026-47262 — image-triggered runtime DoS
These are CRI-runtime-level, not build tooling, so they were in scope but missing. They're wired into check 52's existing containerd probe with a branch-aware verdict: a reachable binary below its branch fix renders a definitive CONFIRMED finding, at/above is cleared, and an unrecognised branch is left unknown — never "safe". Same mechanism the runc CVEs already use. containerd underpins EKS/ECS/Fargate/Bottlerocket/Amazon Linux, so managed nodes are in scope until patched.
CrackArmor — Qualys AppArmor LSM flaws
Anchor entry CVE-2026-23268 carries the full eleven-CVE set. These are confused-deputy plus use-after-free / double-free bugs in the kernel's AppArmor code, present since v4.11 (2017): local root, removal of AppArmor confinement, KASLR/memory leak, and DoS — Qualys demonstrated root on Ubuntu 24.04.3 and Debian 13.1. It matters here because AppArmor is Docker's default MAC layer, and check 11 only reports AppArmor enforcement status, not a flaw in the AppArmor code itself. Fixes are distro-backported, so it's a kernel_version entry with vendor_defer: "consult advisory" on a tracked distro, "unknown" (never safe) on an unrecognised vanilla kernel.
Notes
VERIFY markers remain on two CVSS scores (CVE-2026-53489, -47262), the exact containerd 1.7.x lower bound, and CrackArmor's per-distro fixed versions — confirm against the vendor advisory before relying on them for automated scoring.
Still out of scope: the Leaky Vessels BuildKit siblings (image-build tooling). Not yet encodable: the Project Glasswing / Mythos Linux LPE (under disclosure embargo — no public CVE ID or fix commit).
Update by re-pulling cve_checks.conf (or the release bundle); the database versions independently of the script.
https://github.com/liamromanis101/K8s-container_escape_audit/releases/tag/v4.7.4
3 reactions · 0 comments