CVE
GitLab authorization bypass in Kubernetes workspaces
Affects GitLab CE/EE from 17.6 before the fixed releases, in clusters connected through the GitLab agent for Kubernetes with workspaces. Fixed in 19.3.9, 19.4.8 and 19.5.6.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 19.3.9, 19.4.8, 19.5.6
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected GitLab CE/EE versions: 17.6 up to fixed releases 19.3.9, 19.4.8 and 19.5.6 Clusters connected through the GitLab agent for Kubernetes, with the bug in workspaces
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
GitLab has remediated an issue 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 that under certain conditions could have allowed an authenticated user to read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes due to incorrect authorization in workspaces.
Who should check
Teams running GitLab CE/EE from 17.6 up to the fixed releases 19.3.9, 19.4.8 or 19.5.6 that use workspaces with the GitLab agent for Kubernetes
“all versions from 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach14/20Affects GitLab (an enterprise product or network appliance)
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected GitLab CE/EE versions: 17.6 up to fixed releases 19.3.9, 19.4.8 and 19.5.6 Clusters connected through the GitLab agent for Kubernetes, with the bug in workspacesUpgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-97187 (Incorrect Authorization in GitLab), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-97187 (entry last updated 2026-11-17):
Affected:
- GitLab GitLab: from 17.6, fixed in 19.3.9; from 19.4, fixed in 19.4.8; from 19.5, fixed in 19.5.6
Fixed versions: 19.3.9, 19.4.8, 19.5.6.
Conditions (all must be true for the bug to be hit):
- Affected GitLab CE/EE versions: 17.6 up to fixed releases 19.3.9, 19.4.8 and 19.5.6 (source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/)
- Clusters connected through the GitLab agent for Kubernetes, with the bug in workspaces (source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-97187 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-97187 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/work_items/1197
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/
- https://www.cve.org/CVERecord?id=CVE-2026-97187
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-97187
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-97187"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- GitLab GitLab
From 17.6 · fixed in 19.3.9; From 19.4 · fixed in 19.4.8; From 19.5 · fixed in 19.5.6
Evidence 4
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97187
Is CVE-2026-97187 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes, because of incorrect authorization in workspaces.Source: docs.gitlab.com, cve.org
Which versions are affected by CVE-2026-97187?
GitLab: from 17.6 before 19.3.9; from 19.4 before 19.4.8; from 19.5 before 19.5.6.Source: cve.now feed data
Am I affected, and how do I check?
The affected versions are GitLab CE/EE 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The bug concerns clusters connected through the GitLab agent for Kubernetes, with workspaces. To check, compare the GitLab version of the instance with these ranges and check whether clusters are connected through the GitLab agent for Kubernetes.Source: docs.gitlab.com, cve.org
How do I fix CVE-2026-97187?
Upgrade to GitLab 19.3.9, 19.4.8, 19.5.6 or above.Source: docs.gitlab.com, cve.org