Skip to content
VulniPulse
High8.6GitLab

High [CVE-2026-12053] 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

This high-severity GitLab advisory covers CVE-2026-12053 affecting GitLab EE, GitLab.

CVE-2026-12053 Published Jun 25, 2026Updated by vendor Jun 26, 2026
Affected products & platforms
GitLabGitLab CE / EE
Open vendor advisory

Android app · Google Play

Monitor future GitLab CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected versions
  • before 19.1.1

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 19.1.1

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

Upgrade to a fixed release: 19.1.1. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.