GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: Duo Agent Platform shows unredacted secret values from secret detection findings

CVSS 4.3CVE-2026-115736Control plane, storage & DevOpscurated

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

All Control plane, storage & DevOps entries

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.