Is CVE-2026-46604 exploited in the wild?

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

How severe is CVE-2026-46604?

Informational severity, with a CVSS score of 5.3, published 26 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-46604?

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-46604 attacked?

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

Am I affected by CVE-2026-46604?

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-46604: Go x/image/tiff denial of service via out-of-bounds strip offset

CVE-2026-46604 · Severity: info · CVSS 5.3 · Published 2026-06-26

A vulnerability exists in the Go programming language's TIFF image processing library. An attacker can provide a specially crafted, invalid TIFF image that causes the application to crash (panic) when it attempts to decode the file. This can lead to a denial-of-service, where the affected service becomes unavailable to users.

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

Quick answers

Is CVE-2026-46604 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46604 being exploited in the wild.
How severe is CVE-2026-46604?: Informational severity, with a CVSS score of 5.3, published 26 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-46604?: 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-46604 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46604?: 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

A denial-of-service vulnerability exists in the golang.org/x/image/tiff package due to improper validation of strip offsets during TIFF image decoding. When the `Decode` function encounters an invalid image containing an out-of-bounds strip offset, it triggers a runtime panic rather than returning an error. This can be exploited by a remote, unauthenticated attacker who provides a malicious TIFF file to an application using this library. The issue is resolved in version v0.43.0 of the golang.org/x/image module.

Affected products

Go Project golang.org/x/image/tiff before v0.43.0

Identifiers

CVE-2026-46604
GO-2026-5066

Timeline

2026-06-23: disclosed: Issue reported to Go project
2026-06-26: advisory: CVE-2026-46604 published
2026-06-26: patched: Fix released in v0.43.0

References

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