Skip to main content
CVE-2026-118961VulnerabilityPublished

GitLab CE/EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118961· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 19.5.6 : update GitLab when convenient.

Data as of 17 Nov 2026, 07:52 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.15.3
Patch
Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade GitLab to 19.5.6, 19.4.8 or 19.3.9.

Affected software

ProductAffectedFixed in
GitLabGitLabAffected
  • >=19.5 <19.5.6
Fixed in
  • 19.5.6
GitLabGitLabAffected
  • >=19.4 <19.4.8
Fixed in
  • 19.4.8
GitLabGitLabAffected
  • >=17.11 <19.3.9
Fixed in
  • 19.3.9
GitHubgitlab-org/gitlabpkg:github/gitlab-org/gitlabOther threatsAffected
  • 17.11 – 19.5.6
6 affected builds
Fixed in–

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

AI-suggested

The issue has been remediated in GitLab CE/EE versions 19.3.9, 19.4.8, and 19.5.6 and later. Users should upgrade to these fixed versions to mitigate the vulnerability. No additional mitigation steps are indicated.

Description

A vulnerability in GitLab CE/EE versions from 17.11 up to but not including 19.3.9, 19.4 up to but not including 19.4.8, and 19.5 up to but not including 19.5.6 allowed unauthenticated users to read commit comments from private source forks via public project merge request discussions due to missing authorization checks. This issue has been remediated in the specified fixed versions.

References

Community reviews

Loading reviews…