Is CVE-2026-46602 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46602 being exploited in the wild.

How severe is CVE-2026-46602?

Informational severity, with a CVSS score of 0, published 25 June 2026.

Which products and versions are affected?

golang.org/x/image (Go) SEMVER:introduced=0,fixed=0.43.0.

Is there a fix for CVE-2026-46602?

Yes. golang.org/x/image (Go): upgrade to 0.43.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46602 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-46602?

Check whether you run golang.org/x/image (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46602: Go x/image/tiff unbounded memory consumption in TIFF decoder

CVE-2026-46602 · Severity: info · CVSS 0 · Published 2026-06-25

A vulnerability in the Go programming language's TIFF image processing library allows for a denial-of-service attack. By providing a specially crafted or corrupt TIFF image with excessively large internal 'tiles,' an attacker can force the application to consume all available system memory. This can lead to application crashes, service outages, and general system instability.

Technologies: golang.org/x/image (Go). Vendors: Go.

Quick answers

Is CVE-2026-46602 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46602 being exploited in the wild.
How severe is CVE-2026-46602?: Informational severity, with a CVSS score of 0, published 25 June 2026.
Which products and versions are affected?: golang.org/x/image (Go) SEMVER:introduced=0,fixed=0.43.0.
Is there a fix for CVE-2026-46602?: Yes. golang.org/x/image (Go): upgrade to 0.43.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46602 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46602?: Check whether you run golang.org/x/image (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

golang.org/x/image (Go): upgrade to 0.43.0 or later
```
go get golang.org/x/image@v0.43.0
```

Technical details

The vulnerability is an uncontrolled resource consumption issue within the TIFF decoder of the golang.org/x/image/tiff package. Specifically, the decoder fails to validate or limit the dimensions of tiles within tiled TIFF images, which can be defined as larger than the actual image dimensions. An attacker can exploit this by providing a malicious TIFF file that, when processed by the Decode function, triggers unbounded memory allocation. This can result in a Denial of Service (DoS) via memory exhaustion. The issue is fixed in version 0.43.0 of the package.

Affected products

Go Project golang.org/x/image/tiff < 0.43.0

Identifiers

CVE-2026-46602
GO-2026-5062

Timeline

2026-06-08: disclosed: Issue reported to Go project
2026-06-18: advisory: Go Vulnerability Database entry published
2026-06-25: advisory: NVD entry published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.