CVE-2026-16627: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certa

Routine

HIGH 7.7UPGRADE

CVE-2026-16627 is a high-severity flaw (CVSS 7.7) 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 CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sanitization of HTML content rendered in a CI job modal.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-08-12
Last modified	2026-08-19

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

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

Am I affected?

Timeline

2026-08-12 18:17 UTCPublished CVE record published
2026-08-19 15:59 UTCUpdated Record last modified

gitlab gitlab UPGRADE

Affected: >= 19.2.0 and < 19.2.2

Fixed in: 19.2.2

Safe to downgrade to: a release before 19.2.0

1. Check installed version

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

2. UPGRADE to 19.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitlab

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitlab

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 19.2.0 (Debian / Ubuntu)

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

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitlab sudo dnf downgrade gitlab-<VERSION_BEFORE_19.2.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.

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-16627?

gitlab: upgrade to 19.2.2. Exact commands for each OS are on this page.

Is CVE-2026-16627 being exploited?

CVE-2026-16627 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-16627 affect?

CVE-2026-16627 affects gitlab. Severity is high (CVSS 7.7). GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sani

How urgent is CVE-2026-16627?

Priority 37/100. High severity

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