CVE-2026-5318 describes an out-of-bounds write in LibRaw up to version 0.22.0. The flaw is in HuffTable::initval in src/decompressors/losslessjpeg.cpp, within the JPEG DHT parser. According to the provided content, manipulation of the bits[] argument can cause memory to be written past the intended bounds during Huffman table initialization while parsing a specially crafted image file. The issue is remotely triggerable via malicious input files processed by affected LibRaw-based applications. The content also states that CVE-2026-5318 appears to be a duplicate of TALOS-2026-2330 / CVE-2026-20911, which is characterized as a heap-based buffer overflow in the same function.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.