CVE-2026-71502: Stored client-side template injection in CTI-Transmute
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.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary JavaScript execution in the victim's browser under the CTI-Transmute origin. This can expose any data available to the victim through the application, including sensitive tokens or API keys rendered into the page, enable authenticated actions using the victim's session, and permit modification of conversions or other application data. If an administrator views the malicious content, the attacker may achieve higher-impact actions available to administrative users.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by disabling or tightly restricting unauthenticated creation of public conversions and other untrusted user-controlled content that is rendered into Vue-compiled views. Restrict access to affected pages where possible, and minimize administrator exposure to untrusted public content. Review whether the Vue runtime compiler is enabled in production-rendered views and remove unnecessary dynamic template compilation where feasible. These measures are temporary and do not replace vendor remediation.
Remediation
Patch, then assume compromise.
Upgrade to CTI-Transmute 1.5 or later. The fix registers a global Jinja finalize hook that inserts a zero-width Unicode word joiner into Vue delimiter sequences found in server-rendered values, preventing Vue from recognizing attacker-controlled content as template expressions while preserving visible rendering. Ensure all affected deployments are updated and regression-tested against stored template-expression injection paths in public conversion content and related user-controlled fields.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-71502 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-71502 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-71502?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-71502.
- Is there a patch for CVE-2026-71502?
- Upgrade to CTI-Transmute 1.5 or later. The fix registers a global Jinja finalize hook that inserts a zero-width Unicode word joiner into Vue delimiter sequences found in server-rendered values, preventing Vue from recognizing attacker-controlled content as template expressions while preserving visible rendering.
- How severe is CVE-2026-71502?
- CVE-2026-71502 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.74% (55th percentile) as of Sep 25, 2026.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.