Live › vulnerability › CVE-2026-113951
Go to dashboardContainer, Apple's tool for running Linux containers on macOS, lets an attacker who can write to a k8s cluster container's filesystem plant an exec credential plugin in /etc/kubernetes/admin.conf. When a user later pulls that kubeconfig to the host with container k8s write-config or create and runs kubectl, the plugin executes as the macOS host user, giving the attacker arbitrary command execution on the host.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Developers and teams on macOS who run Container with its Kubernetes support (container k8s) and pull kubeconfig from cluster containers onto the host. Exposure requires a container in the cluster that an attacker can write to, so teams that do not use container k8s or run only trusted containers face lower risk.
No product ranges from the sources yet.
container --version and compare it against 1.5.0.container k8s usage on the host, and check whether kubeconfig files written by container k8s write-config contain an exec: credential plugin block.1.5.0 or later.exec: entries before running kubectl against it.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
If an attacker can write to the filesystem of a container k8s cluster container, they can plant an exec credential plugin in /etc/kubernetes/admin.conf. kubectl will run that plugin as the macOS host user the next time someone pulls the cluster's kubeconfig onto the host with container k8s write-config or create and then runs kubectl against it — turning filesystem access inside an untrusted Linux container into arbitrary command execution on the host. This vulnerability is addressed in Container version 1.5.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-113951")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.