CVE-2026-1230 [Medium] | Security Vulnerability in Gitlab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 1.0 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to cause repository downloads to contain different code than displayed in the web interface due to incorrect validation of branch references under certain circumstances.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-12	0.04%	0.05%	+0.01%
2	2026-03-12	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-12

0.04%

0.05%

+0.01%

2026-03-12

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.1	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.3	1.4	[email protected]
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	2.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.1

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.3

1.4

[email protected]

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

2.8

3.6

[email protected]

OS Trackers for CVE-2026-1230

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2026-1230 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): open 1.	https://security-tracker.debian.org/tracker/CVE-2026-1230
`ubuntu`	medium	CVE-2026-1230 medium priority: Ubuntu including 1 source packages (gitlab), 5 status rows across 5 suites (jammy, noble, questing, upstream, xenial): DNE 3, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2026-1230

Affected software / configurations for CVE-2026-1230

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 1.0.0, < 18.7.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 1.0.0, < 18.7.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.8.0, < 18.8.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.8.0, < 18.8.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.9.0, < 18.9.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.9.0, < 18.9.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2026-1230

URL	Tags
https://about.gitlab.com/releases/2026/03/11/patch-release-gitlab-18-9-2-released/	Release Notes Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/work_items/587002	Broken Link
https://hackerone.com/reports/3505165	Permissions Required

URL

CVE-2026-1230 | Use of Incorrectly-Resolved Name or Reference in GitLab

Exploit prediction scoring system (EPSS) score for CVE-2026-1230

Common vulnerability scoring system (CVSS) metrics for CVE-2026-1230

Weakness enumeration for CVE-2026-1230

OS Trackers for CVE-2026-1230

Affected software / configurations for CVE-2026-1230

References for CVE-2026-1230