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

HTML injection in GitLab CE/EE test case titles

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

CVE-2026-0595 is an authenticated HTML injection vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). It affects all versions from 13.9 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4. Under certain conditions, an authenticated user could inject HTML through test case titles, which could then be leveraged to add unauthorized email addresses to a victim user's account. The issue is described by GitLab as an HTML injection flaw in test case titles that can impact account integrity.

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.

Successful exploitation can allow an authenticated attacker to add unauthorized email addresses to another user's GitLab account. This creates an account integrity compromise and may enable follow-on abuse of email-based account functions, including potential account takeover or unauthorized access depending on the victim account's configuration and available recovery or notification workflows.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting access to authenticated users who can create or modify test case titles, closely monitoring for unexpected account email-address changes, and reviewing audit trails or account-management events for unauthorized additions. GitLab.com is already patched. No specific vendor mitigation beyond upgrading was provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. GitLab states the issue is remediated in 18.6.6, 18.7.4, and 18.8.4. Self-managed installations should upgrade immediately to a patched version appropriate for their release train.
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.

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 activity2

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