CVE-2026-2995VulnerabilityPublished 27 Mar 2026Updated 10 Sep 2026

CVE-2026-2995: GitLab · Improper Neutralization of Script-Related HTML Tags

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.10.1 : patch gitlab soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.10.1, 18.9.3, 18.8.7

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 18.10.1, 18.9.3 or 18.8.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.4.0 <18.8.7 >=18.9.0 <18.9.3 >=18.10.0 <18.10.1	Fixed in 18.8.7 18.9.3 18.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released by GitLab. Users should upgrade affected GitLab EE instances to versions 18.8.7, 18.9.3, 18.10.1 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

GitLab EE versions from 15.4 up to but not including 18.8.7, 18.9 up to but not including 18.9.3, and 18.10 up to but not including 18.10.1 contain a vulnerability involving improper sanitization of HTML content. This flaw could allow an authenticated user to add email addresses to targeted user accounts. The issue has been remediated in later versions.

Impact

An authenticated attacker could exploit this vulnerability to add email addresses to targeted user accounts, potentially leading to unauthorized account modifications or social engineering attacks. The impact is limited to authenticated users and does not indicate remote unauthenticated exploitation.

Summary

CVE-2026-2995 describes a vulnerability in GitLab EE where improper neutralization of script-related HTML tags (a basic cross-site scripting issue) could be exploited by an authenticated user to add email addresses to other user accounts. The vulnerability affects versions >=15.4.0 <18.8.7, >=18.9.0 <18.9.3, and >=18.10.0 <18.10.1. GitLab has issued patches that fix this issue in versions 18.8.7, 18.9.3, and 18.10.1 and later.

References

Community reviews

Loading reviews…