Loading vulnerability…
CVE-2026-8080 is a stored cross-site scripting vulnerability in MISP affecting versions before 2.5.37. The flaw is in the old templating engine's template element attribute handling logic, where the application accepted arbitrary values for TemplateElementAttribute type and category fields without validating them against known MISP attribute type and category definitions. An attacker with permission to create or modify template element attributes could persist a crafted type value that is later rendered in the web interface, resulting in stored XSS.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small Python proof-of-concept for a DKIM signature verification bypass described as CVE-2026-8080. It contains two code files: dkim_verifier_sim.py, which is the main demonstration, and exploit_dkim_bypass.py, which is only a stub that instructs the user to run the simulator. The core script builds a hardcoded raw email containing From, To, Subject, DKIM-Signature, and an extra X-Extra header, then parses headers and simulates flawed DKIM verification logic. The vulnerability modeled is a header canonicalization error: instead of verifying only the headers listed in the DKIM h= tag, the verifier also includes an extra header present in the message. The script then prints that verification passed incorrectly, illustrating how a vulnerable implementation could accept a modified message. There is no real network interaction, no live SMTP delivery, no cryptographic verification, and no weaponized payload; this is a conceptual local simulation of an email-based attack path. The repository’s purpose is educational/demonstrative rather than operational exploitation.
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.