CVE-2026-36849 is a denial-of-service vulnerability affecting libtiff 4.7.1 and earlier. Processing a crafted TIFF file containing an excessively large SamplesPerPixel tag value can trigger denial of service. The specific vulnerable function and underlying failure mechanism are not established.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability affecting libtiff 4.7.1 and earlier, triggered by processing a crafted TIFF file with a large SamplesPerPixel tag value. The advisory identifies affected libtiff packages on EulerOS 2.0 SP15 and recommends updating them. Nessus identifies exposure using self-reported package versions rather than testing exploitation.
A denial-of-service vulnerability affecting libtiff 4.7.1 and earlier, triggered by processing a crafted TIFF file with a large SamplesPerPixel tag value. The EulerOS advisory identifies affected libtiff packages and recommends updating them.
A vulnerability affecting the tiff library and related packages. The advisory assigns a CVSS v3 score of 6.5; its vector indicates network-based exploitation requiring user interaction, with high availability impact and no confidentiality or integrity impact. The content does not describe the underlying flaw. The patch publication date is June 17, 2026.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.