CVE-2026-71502 is a stored client-side template injection vulnerability in CTI-Transmute affecting versions 1.4 and earlier. The flaw is caused by insufficient neutralization of Vue template expression delimiters in server-rendered, user-controlled content. Public conversion names and descriptions, and potentially user profile names, can be attacker-controlled and are rendered into a DOM region later compiled by Vue using configured [[ ... ]] delimiters. Although Jinja HTML escaping is applied, the escaped value is still interpreted by Vue as a template expression rather than inert text. An unauthenticated attacker can therefore store a malicious Vue expression that accesses the JavaScript Function constructor, for example through constructor chaining, and execute arbitrary JavaScript in the browser context of the CTI-Transmute origin whenever another user views the affected page. The issue is persistent and triggers on page view of affected content, including public conversion detail pages.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.