Skip to main content
VulnerabilityPublished

CVE-2026-18491: GitLab · Incorrect Authorization

Affects GitLabSource CVE Database V5

0
Compare

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

Data as of 17 Nov 2026, 04:35 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 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

CPE configurations (1)

  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*

AI-suggested

Upgrade GitLab CE/EE to version 19.3.9, 19.4.8, or 19.5.6 or later, where this vulnerability has been fixed. No other mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-18491 is an authorization vulnerability in GitLab CE/EE versions 19.2 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. It allows an authenticated user with a granular personal access token of limited scope to gain Kubernetes API proxy access beyond the token's intended permissions due to missing enforcement of scope in the Kubernetes agent proxy-user authorization flow. The issue has been fixed in versions 19.3.9, 19.4.8, and 19.5.6.

References

Community reviews

Loading reviews…