Is CVE-2026-33809 exploited in the wild?

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

How severe is CVE-2026-33809?

Medium severity, with a CVSS score of 5.3, published 25 March 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-33809?

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

Am I affected by CVE-2026-33809?

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-33809: Go Images vulnerable to an out-of-memory error via a crafted TIFF file

Q: Is there a fix for CVE-2026-33809?

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

Q: Am I affected by CVE-2026-33809?

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-33809 · Severity: medium · CVSS 5.3 · Published 2026-03-25

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

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

Quick answers

Is CVE-2026-33809 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33809 being exploited in the wild.
How severe is CVE-2026-33809?: Medium severity, with a CVSS score of 5.3, published 25 March 2026.
Which products and versions are affected?: golang.org/x/image (Go) < 0.38.0, SEMVER:introduced=0,fixed=0.38.0.
Is there a fix for CVE-2026-33809?: Yes. golang.org/x/image (Go): upgrade to 0.38.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33809?: 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.38.0 or later
```
go get golang.org/x/image@v0.38.0
```

Affected products

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

Identifiers

CVE-2026-33809
GHSA-44p7-9xx4-hf2g
GO-2026-4815

References

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