CVE-2026-16969 is a stored cross-site scripting vulnerability in the DFIR-IRIS web application, confirmed in version 2.4.26 and possibly affecting additional versions. The flaw is present in the assets functionality, where attacker-controlled asset fields such as names and descriptions can contain arbitrary HTML content. Although output encoding is applied in some views, it is omitted in other application locations, including customer settings, creating a persistent XSS condition when the stored asset data is later rendered. Successful exploitation causes attacker-supplied JavaScript to execute in the browser of another user viewing the affected content. Because the vulnerable data is stored server-side and later rendered in privileged workflows, the issue can be leveraged against higher-privileged users, including administrators.
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.
3 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.