EUVD-2026-39169
GHSA-fwjq-556c-7hwm
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Description says 'a user' and 'under certain conditions', so PR:L and AC:H; remote feature access gives AV:N; only committed data is exposed, so C:H, I:N, A:N.
Primary rating from Vendor (gitlab).
CVSS VectorNVD
Lifecycle Timeline
7DescriptionNVD
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.
Articles & Coverage 2
AnalysisAI
Information disclosure in GitLab Enterprise Edition 19.1 (before 19.1.1) lets a user retrieve sensitive data previously committed to a project because Duo Workflows fails to adequately filter its output under certain conditions. The flaw exposes confidential repository content through GitLab's AI workflow feature without altering or destroying data. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as 'none', though EPSS sits at a modest 0.33% (25th percentile).
Technical ContextAI
The affected component is Duo Workflows, GitLab's AI-assisted automation feature in the Enterprise Edition (CPE cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:enterprise:*). The root cause is classified as CWE-532 (insertion of sensitive information into an output/log channel), here manifesting as insufficient output filtering: data already committed to a project's history is surfaced through the Duo Workflows output rather than being scrubbed or access-checked before presentation. The issue is specific to the EE-only Duo Workflows code path and does not affect Community Edition, which lacks the feature.
RemediationAI
Vendor-released patch: upgrade GitLab EE to 19.1.1 or later as the primary and authoritative fix, per the GitLab patch release at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-1-released/. Self-managed administrators should apply the 19.1.1 patch release immediately. If an upgrade cannot be scheduled at once, a targeted compensating control is to disable the Duo Workflows feature for affected groups/projects, which removes the vulnerable output path at the cost of losing AI workflow automation for users; restricting Duo Workflows usage to trusted members and auditing access to projects containing secrets reduces exposure but does not fully close the gap. Rotate any credentials or secrets that may have been committed to affected repositories, since the underlying sensitive data remains in git history even after patching.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today