Database/Control plane, storage & DevOps
GitLab EE: Duo Agent Platform shows unredacted secret values from secret detection findings
Impact
An authorization check is missing in the GitLab Duo Agent Platform. Under certain conditions, a user can read the raw, unredacted secret values from secret detection findings they can access, where GitLab would normally show them redacted. Those findings are leaked credentials committed to repositories, such as cloud keys, registry tokens and cluster credentials, so reading them in clear text gives that user live access to whatever the secrets unlock. The record does not say what the 'certain conditions' are. Affects GitLab EE 19.1 before 19.3.9, 19.4 before 19.4.8 and 19.5 before 19.5.6.
Who can reach it
An authenticated GitLab user who already has access to the secret detection findings and can use the Duo Agent Platform. Network access to the instance is required.
What to do
Upgrade to 19.3.9, 19.4.8 or 19.5.6 per the GitLab 19.5.6 patch release. On a self-managed instance this is a package upgrade and a service restart, with no fleet impact. Secrets that show up in secret detection findings should be rotated in any case. Treat any finding that was viewable through Duo during the affected window as exposed.
References
Related entries
- GitLab EE: authenticated user can configure GitLab Duo settings for groups without an eligible licenseCVE-2026-122045 · GitLab EE (GitLab Duo group settings)Medium
- GitLab: MCP-scoped OAuth token can approve and merge merge requests beyond its scopeCVE-2026-123142 · GitLab CE/EE (MCP-scoped OAuth token authorization)Medium
- GitLab EE: authenticated user can cause a denial of service in Duo usage analytics via crafted inputCVE-2026-125920 · GitLab EE (Duo usage analytics)Medium
- GitLab EE: Duo Workflow session can start with more privileges than its foundational flow declaresCVE-2026-128849 · GitLab EE (Duo Workflow / foundational flows)Medium
- GitLab EE: developer-role user can bypass admin AI tool governance controls in a governed namespaceCVE-2026-129253 · GitLab EE (AI tool governance controls for workflows)Medium
- GitLab CE/EE: planner-role user can set a future merge schedule date on their own merge requestsCVE-2026-129321 · GitLab CE/EE (merge request scheduled merge)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.