dbcve.org
GitLabApplication

CVE-2026-12053

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab EE versions 19.1 before 19.1.1 contains an information disclosure vulnerability in the Duo Workflows feature. Due to insufficient output filtering, an authenticated user could under certain conditions access sensitive information that had already been committed to a project, even if they would not normally have authorization to view that content.

MitigationUpgrade GitLab EE to version 19.1.1 or later to remediate this vulnerability. Organizations should also review commit history for any unauthorized access during the vulnerable period.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:= 19.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed GitLab EE version
    Run `gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version to determine the exact version number
    Affected if The installed version is exactly 19.1.0 (no other versions are listed as affected)
  2. Confirm the GitLab edition is Enterprise Edition (EE)
    Check the GitLab admin panel or run `gitlab-rake gitlab:env:info` to verify the edition
    Affected if The product is GitLab EE (this vulnerability affects only Enterprise Edition, not CE)
  3. Determine if Duo Workflows is enabled
    Check the GitLab instance settings under AI/ML settings or Duo settings in the admin panel, or inspect the gitlab_rails.rb configuration file for duo_workflows_enabled setting
    Affected if Duo Workflows feature is enabled on the instance (this is the vulnerable module)
  4. Review audit logs for suspicious Duo Workflows access
    Search GitLab audit logs for events involving Duo Workflows and file/repository access, filtering for the time period since 19.1.0 deployment
    Affected if Any audit entries show authenticated users accessing files through Duo Workflows that they would not normally have permission to view

You are affected if GitLab EE version is exactly 19.1.0 AND Duo Workflows feature is enabled, allowing authenticated users potentially unauthorized access to committed content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GitLab EE to version 19.1.1 or later to remediate this vulnerability. Organizations should also review commit history for any unauthorized access during the vulnerable period.

Recommended fix High confidence

19.1.1

  1. Verify current GitLab installation version using the GitLab Rails console or admin interface
  2. Plan maintenance window for the upgrade process
  3. Back up the GitLab database, repositories, and configuration files
  4. Consult official GitLab upgrade documentation for version 19.1.1
  5. Execute upgrade to GitLab version 19.1.1 following standard upgrade procedures
  6. Verify the upgrade was successful and GitLab is functioning properly
  7. Confirm the version number matches 19.1.1 in the admin interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data