Application crash via truncated TIFF strip offset
Published Jun 26, 2026 · Updated Jun 26, 2026
Denial of service in Go Project golang.org/x/image/tiff before 0.43.0 allows remote attackers to crash applications via crafted TIFF images. The Decode path converts attacker-controlled 64-bit strip offsets and byte counts to int before buffer.Slice checks the resulting slice bounds. The panic occurs only on 32-bit builds when Decode receives an invalid offset that overflows int, interrupting the consuming process without corrupting data.
Summary
What happened
Denial of service in Go Project golang.org/x/image/tiff before 0.43.0 allows remote attackers to crash applications via crafted TIFF images. The Decode path converts attacker-controlled 64-bit strip offsets and byte counts to int before buffer.Slice checks the resulting slice bounds. The panic occurs only on 32-bit builds when Decode receives an invalid offset that overflows int, interrupting the consuming process without corrupting data.
The record
- CVE
- CVE-2026-46604
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- golang.org/x/image
- Product
- golang.org/x/image/tiff
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.43.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo