# CVE-2026-113951: 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.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026

## What is CVE-2026-113951?

CVE-2026-113951 is a vulnerability in Apple Container, published on 23 Oct 2026. 

### Official description

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.

## Which versions are affected by CVE-2026-113951?


## How do I fix CVE-2026-113951?

No fix has been published for CVE-2026-113951 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113951 being exploited?

There is no known exploitation of CVE-2026-113951 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113951 and fix it if it is affected.

What it is: CVE-2026-113951 is a vulnerability in Apple Container, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113951 in the wild and no public exploit code.

Affected product: Apple Container. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113951/ (Markdown: https://insights.sbomify.com/CVE-2026-113951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113951
- OSV: https://osv.dev/vulnerability/CVE-2026-113951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113951/
Summaries are generated and may contain mistakes; the official description above is the record.