# CVE-2026-113957: An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pul


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

## What is CVE-2026-113957?

CVE-2026-113957 is a vulnerability in Apple container, published on 29 Oct 2026. 

### Official description

An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pull by digest, so that a user runs an image other than the one they pinned. The fix compares the returned digest to the pinned digest and fails the pull on a mismatch. Tag pulls are exempt, because a tag is mutable by design. The fix also verifies the hash of manifests and blobs when they are fetched. This vulnerability is addressed in container version 1.6.0 and containerization version 0.52.1.

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


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

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

## Is CVE-2026-113957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113957 is a vulnerability in Apple container, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113957 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-113957/ (Markdown: https://insights.sbomify.com/CVE-2026-113957/index.md)
```

## Sources

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

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