Skip to main content
CVE-2026-97187VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97187· High 7.6

Not known to be exploited · CVSS 7.6 High · fixed in 19.5.6 : patch GitLab soon.

Data as of 17 Nov 2026, 07:51 UTC

CVSS 3.1 base score
7.6High
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.17.6
Patch
Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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
  • >=17.6 <19.3.9
Fixed in
  • 19.3.9

AI-suggested

Upgrade GitLab CE/EE to versions 19.3.9, 19.4.8, 19.5.6, or later to remediate this vulnerability. These versions contain the official fix for the authorization issue. No additional mitigations are indicated by the vendor advisory.

Description

A vulnerability in GitLab CE/EE versions from 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 could allow an authenticated user to read Kubernetes Secrets from other namespaces in clusters connected via the GitLab agent for Kubernetes. This occurs due to incorrect authorization in workspaces. The issue has been remediated in the specified fixed versions.

References

Community reviews

Loading reviews…