Home/CVE/A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excess
CVE
↯ PDF report Light Dark

CVE-2026-33809

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excess

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.

MEDIUM · CVSS 5.3 EPSS 0.00013
EPSS exploitation odds0.01% · top 97%
Schedule remediation
  • SSVC automatable: yes - attacks can be scripted at scale
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-33809, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

Severity & exploitation scoring

View on NVD →
CVSS base score
5.3
MEDIUMCVSS v3.1 · [email protected]
EPSS exploitation probability
0.01%
Top 97%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Lifecycle
  1. 25 Mar 2026Published to NVD
  2. 21 Apr 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.

ATT&CK techniques

1

Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.

▤ Build a SIEM detection for these techniques

CAPEC attack patterns

1

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

Weakness Classification

Affected Products & Versions

1
golang tiff< 0.38.0

Affected Packages

1
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Go golang.org/x/image fixed in 0.38.0

Vendor Advisories

3
suse-csafopenSUSE-SU-2026:10628-1
rhsaRHSA-2026:7385Important
rhsaRHSA-2026:7291Important
🔗

References & Sources

3
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.