Skip to main content
CVE-2026-18491VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18491· Medium 4.9

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

Data as of 17 Nov 2026, 07:53 UTC

CVSS 3.1 base score
4.9Medium
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.14.9
Patch
Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/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 and gitlab/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
  • >=19.2 <19.3.9
Fixed in
  • 19.3.9
RubyGemsgitlab/gitlabpkg:gem/gitlab/gitlabOther threatsAffected
  • 19.2 <19.3.9
  • 19.4 <19.4.8
  • 19.5 <19.5.6
Fixed in
  • 19.3.9
  • 19.4.8
  • 19.5.6

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

AI-suggested

GitLab has released official fixes in versions 19.3.9, 19.4.8, and 19.5.6 that address this vulnerability. Users should upgrade affected GitLab CE/EE instances to these or later versions to remediate the issue. No additional mitigation steps are indicated beyond applying the official patches.

Description

A vulnerability in GitLab CE/EE versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 allowed authenticated users with a granular personal access token to gain Kubernetes API proxy access beyond their token's intended scope due to missing enforcement of granular scopes in the Kubernetes agent proxy-user authorization flow. This issue has been remediated by GitLab.

References

Community reviews

Loading reviews…