GitLab CE/EE Service Desk email template Support Bot impersonation and content injection
CVE-2026-9694 is an improper neutralization flaw in GitLab Community Edition and Enterprise Edition Service Desk email template processing. It affects all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, a remote unauthenticated attacker can send a specially crafted Service Desk email reply that is processed in a way that does not properly neutralize attacker-controlled content, allowing the attacker to impersonate the GitLab Support Bot and inject arbitrary content into the resulting message flow.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Impersonation vulnerability in GitLab that allows an unauthenticated user to impersonate the official GitLab Support Bot by injecting arbitrary content via a Service Desk email reply.
Improper neutralization vulnerability in GitLab CE/EE Service Desk email template processing that could allow impersonation of the GitLab Support Bot and arbitrary content injection via crafted email replies.
The version that knows your environment.
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.