CVE-2026-97187: 
GitLab vulnerability analysis and mitigation

Overview

CVE-2026-97187 is an incorrect authorization vulnerability in GitLab CE/EE affecting all versions from 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. Under certain conditions, an authenticated user could read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes due to a flaw in workspace authorization logic. The vulnerability was published on November 17, 2026, and has a CVSS v3.1 base score of 7.6 (High) (GitHub Advisory, GitLab Patch Release).

Technical details

The root cause is classified as CWE-863 (Incorrect Authorization): the GitLab workspaces feature does not correctly enforce namespace-level access controls when interacting with Kubernetes clusters connected via the GitLab agent. An authenticated user with high-level privileges can exploit this flaw over the network without user interaction, causing the authorization boundary to be crossed (scope change) and allowing reads of Kubernetes Secrets belonging to other namespaces. The issue was reported via HackerOne (report #3975310) and tracked in the GitLab agent project (GitHub Advisory, GitLab Agent Issue).

Impact

Successful exploitation allows an authenticated, high-privileged GitLab user to read Kubernetes Secrets stored in namespaces they should not have access to across any Kubernetes cluster connected through the GitLab agent. This can expose sensitive credentials such as API keys, service account tokens, TLS certificates, and database passwords stored as Kubernetes Secrets, potentially enabling lateral movement within the connected cluster infrastructure. Integrity impact is rated low (limited unintended modification possible), and availability is not affected (GitHub Advisory, GitLab Patch Release).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of disclosure (Feedly). The EPSS score is approximately 0.0027 (0.27%), indicating a low near-term probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an authenticated account with high privileges, which limits the attacker pool but does not eliminate risk in multi-tenant or shared GitLab environments.

Indicators of compromise

  • Logs: GitLab application logs showing authenticated requests to workspace or Kubernetes agent endpoints accessing Secrets in namespaces not associated with the user's projects; unexpected cross-namespace Kubernetes API calls originating from the GitLab agent.
  • Kubernetes Audit Logs: get or list operations on secrets resources in namespaces not owned by the requesting GitLab workspace, attributed to the GitLab agent service account.
  • Network: Unusual outbound data transfers from the GitLab agent pod to external destinations following Secret reads.

Mitigation and workarounds

GitLab has released patched versions addressing this vulnerability: 19.3.9, 19.4.8, and 19.5.6. Organizations should upgrade to the appropriate patched version immediately based on their current release branch. As an interim measure if patching is not immediately possible, administrators should review Kubernetes audit logs for unauthorized cross-namespace Secret reads and restrict high-privilege user access to GitLab workspaces until the patch is applied (GitLab Patch Release, GitHub Advisory).

Community reactions

The vulnerability was part of a broader GitLab patch release addressing 37 security bugs, which received coverage from security news outlets including GBHackers and CyberPress (GBHackers, CyberPress). Security community discussion was noted on Mastodon and infosec.exchange, though no major researcher commentary specific to this CVE has been identified. The vulnerability was also flagged by national CERTs including AUSCERT, INCIBE, and CCN-CERT.

Additional resources


Source: This report was generated using AI

Related GitLab vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-18241HIGH8.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-97187HIGH7.6
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-85778MEDIUM6.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-16609MEDIUM5.4
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-18491MEDIUM4.9
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management