Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

HTML injection in GitLab EE vulnerability report feature leading to unauthorized email address addition

IdentifiersCVE-2026-2995CWE-79· Improper Neutralization of Input…

CVE-2026-2995 is an HTML injection issue in GitLab Enterprise Edition (EE) affecting all versions from 15.4 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. The flaw is in the vulnerability report feature, where improper sanitization of HTML content allows an authenticated user to inject crafted HTML. Successful exploitation can cause unauthorized email addresses to be added to a targeted user's account, creating a path toward account compromise.

Share:
For your environment

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.

ANALYST BRIEF

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.

An authenticated attacker can manipulate the vulnerability report feature to add attacker-controlled email addresses to another user's account. This can undermine account integrity and may enable subsequent account takeover scenarios, depending on how email-based account management, notifications, or recovery workflows are configured in the affected GitLab deployment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the vulnerability report feature to only highly trusted authenticated users, reduce the number of users permitted to submit or manipulate HTML-bearing content in that workflow, and closely monitor for unauthorized changes to user email addresses. Review audit logs and account-change events for suspicious email additions until upgrades can be completed.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release: 18.8.7 or later, 18.9.3 or later, or 18.10.1 or later, depending on the supported upgrade path. Ensure all affected instances running versions from 15.4 onward are updated to a remediated version.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

7 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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.