VulnerabilityPublished 13 Mar 2026Updated 10 Sep 2026

CVE-2026-1230: GitLab · Use of Incorrectly-Resolved Name or Reference

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.9.2 : update gitlab when convenient.

Data as of 26 Oct 2026, 10:12 UTC

Severity

Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.9.2, 18.8.6, 18.7.6

Exploitation evidence

Disclosed: evidence found.
CVE published 13 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.9.2, 18.8.6 or 18.7.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=1.0.0 <18.7.6 >=18.8.0 <18.8.6 >=18.9.0 <18.9.2	Fixed in 18.7.6 18.8.6 18.9.2

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 users should upgrade to GitLab CE/EE versions 18.7.6, 18.8.6, or 18.9.2 or later to remediate this vulnerability.

Description

A vulnerability in GitLab CE/EE versions from 1.0 up to but excluding 18.7.6, 18.8 up to but excluding 18.8.6, and 18.9 up to but excluding 18.9.2 allows an authenticated user to cause repository downloads to contain different code than what is displayed in the web interface. This occurs due to incorrect validation of branch references under certain circumstances. The issue has been remediated in the specified fixed versions.

Impact

An authenticated user could cause repository downloads to contain code different from what is displayed in the GitLab web interface. This could lead to confusion, potential code integrity issues, or trust problems in the repository content. There are no known exploits in the wild.

Summary

GitLab CE/EE contained a flaw in the validation of branch references that could cause repository downloads to differ from the code shown in the web interface. This vulnerability affects all versions from 1.0 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2. An authenticated user could exploit this to cause discrepancies between downloaded repository content and the displayed code. The issue has been fixed in versions 18.7.6, 18.8.6, and 18.9.2.

References

Community reviews

Loading reviews…