# CVE-2026-46602: Lack of limit on tile sizes in x/image/tiff in golang.org/x/image

> A malicious TIFF image can cause unbounded memory consumption in the Go image library, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** CLEANSTART-2026-BS64327, CLEANSTART-2026-RD95849, DEBIAN-CVE-2026-46602, GHSA-pwfv-328h-75x9, GO-2026-5062, MINI-3vrv-hj97-vwqh, MINI-448f-6xvj-4rxj, MINI-549q-r39f-cjxw, MINI-5727-mm83-rj7q, MINI-5jjv-59m8-9977, MINI-678q-h327-gcpp, MINI-69pp-wm93-9hvg, MINI-6c3r-cf4g-v3h6, MINI-6cwh-8f84-hqx7, MINI-7vhq-4644-r6vm, MINI-7xf5-hjcv-6pvr, MINI-838h-w5jj-38g8, MINI-8cqv-2745-mhp3, MINI-94c7-x8q9-ccf5, MINI-9q9q-w4jv-mfjg, MINI-fc9p-393c-39j6, MINI-fhx7-vjgg-cvqq, MINI-fqvj-jfph-fh7g, MINI-g5j3-8hph-6h68, MINI-g5j9-f2p6-8pgq, MINI-gg5p-g9w4-8mqr, MINI-h2rm-h2gx-f4q9, MINI-hg25-x85x-6jpr, MINI-hg5m-v45h-jhxv, MINI-hjc6-c746-9529, MINI-jx9f-vrcm-hqjg, MINI-pfm6-r4c5-j647, MINI-pjmh-p86h-p8vg, MINI-qc54-j793-qqh3, MINI-rx5q-jm8v-4785, MINI-xj9x-6m54-jcg7, MINI-xxfg-9gvj-q5mw, UBUNTU-CVE-2026-46602

## What is CVE-2026-46602?

CVE-2026-46602 is a high-severity denial of service vulnerability in golang.org/x/image/tiff, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

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

1 open source package ship an affected version, including golang.org/x/image.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang.org/x/image` | Go | All versions | 0.43.0 |

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

Upgrade golang.org/x/image to 0.43.0 or later.

## Is CVE-2026-46602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46602 is a high-severity denial of service vulnerability in golang.org/x/image/tiff, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46602 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang.org/x/image (Go): affected all versions; fixed in 0.43.0

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-46602/ (Markdown: https://insights.sbomify.com/CVE-2026-46602/index.md)
```

## Sources

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

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