4 ms·

If your container has setuid binaries and these modules are loaded, yes.

• lights0123 5mo ago
  With the exploits published as-is, you'll only get root inside the container: there's no explicit namespace break, and calling setuid() in a container just gives you root in the container. However, it can be used to modify files that are passed into the container (e.g. Docker run -v), or files that are shared with other containers (e.g. other Docker containers sharing the same layers). kube-proxy with Kubernetes happens to share a trusted binary with containers by default, which is how it can be exploited: https://github.com/Percivalll/Copy-Fail-CVE-2026-31431-Kubernetes-PoC https://github.com/Percivalll/Copy-Fail-CVE-2026-31431-Kuber...
• miduil 5mo ago
  It's poisoning the filesystem cache, if you don't have a setuid binary handy you just poison anything else that gets executed by the host.
• awoimbee 5mo ago
  And your containers need to have specific capabilities enabled, which aren't by default on kubernetes and podman.
  • friedr12 5mo ago
    [dead]
• aaronmdjones 5mo ago
  You don't need any setuid binaries. You could just as easily use the vulnerability to add a job to crontab(5) that causes the cron daemon to run whatever you want as root.