# CVE-2026-65918: PyTorch torchvision GIF Decoder Out-of-bounds Heap Read

> Attackers can cause denial of service or disclose heap memory by supplying malicious GIF files to the PyTorch torchvision library.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 17 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-65918, GHSA-xhgh-4jhq-chj3, UBUNTU-CVE-2026-65918

## What is CVE-2026-65918?

CVE-2026-65918 is a high-severity vulnerability in pytorch vision, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PyTorch torchvision through 0.28.0, fixed in commit 4e05dc2, contains an out-of-bounds heap read vulnerability in the GIF decoder's read_from_tensor callback that passes unclamped length to memcpy. Attackers can supply malicious or truncated GIF files to cause denial of service via segmentation fault or disclose adjacent heap memory contents.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linuxfoundation Torchvision.

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

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

## Is CVE-2026-65918 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65918 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65918 is a high-severity vulnerability in pytorch vision, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65918 exists.

Affected product: pytorch vision. 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-65918/ (Markdown: https://insights.sbomify.com/CVE-2026-65918/index.md)
```

## Sources

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

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