CVE-2026-12053: GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain

This month

HIGH 8.6REMOTEDOWNGRADE

CVE-2026-12053 is a high-severity flaw (CVSS 8.6) affecting gitlab. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-532
Published	2026-06-25
Last modified	2026-06-26

Publisher (CNA): GitLab Inc. · Vendor: gitlab

Last updated 2026-06-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-25 05:16 UTCPublished CVE record published
2026-06-26 18:33 UTCUpdated Record last modified

gitlab gitlab DOWNGRADE

Affected: 19.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 19.1.0

1. Check installed version

apt-cache policy gitlab || rpm -q gitlab || gitlab --version

2. No fixed release: DOWNGRADE to a release before 19.1.0 (Debian / Ubuntu)

apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_19.1.0> sudo apt-mark hold gitlab

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitlab sudo dnf downgrade gitlab-<VERSION_BEFORE_19.1.0> sudo dnf versionlock add gitlab

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

GitLab Security Releases: GitLab Patch Release: 19.1.1, 19.0.3, 18.11.6 2026-06-24

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-12053?

gitlab: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-12053 being exploited?

CVE-2026-12053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-12053 affect?

CVE-2026-12053 affects gitlab. Severity is high (CVSS 8.6). 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 insuffic

How urgent is CVE-2026-12053?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Software pages

GitLab vulnerabilities

Related CVEs

CVE-2026-10086 HIGH 8.7 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 16.4 before 18.11.6, 19.0 before 19.0.
CVE-2026-6896 HIGH 8.7 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0
CVE-2026-84284 MEDIUM 5.3 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 19.2.8, 19.3 before 19
CVE-2025-10903 MEDIUM 6.5 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 19.1.7, 19.2 before 19.2.
CVE-2026-82632 LOW 3.1 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 19.2.8, 19.3 before 19.

References

← Back to latest CVEs