CVE-2026-6896: GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0

Routine

HIGH 8.7UPGRADE

CVE-2026-6896 is a high-severity flaw (CVSS 8.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 EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-07-08
Last modified	2026-10-25

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

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

Am I affected?

Timeline

2026-07-08 21:16 UTCPublished CVE record published
2026-10-25 17:10 UTCUpdated Record last modified

gitlab gitlab UPGRADE

Affected: >= 13.11.0 and < 18.11.7 · >= 19.0.0 and < 19.0.4 · >= 19.1.0 and < 19.1.2

Fixed in: 18.11.7, 19.0.4, 19.1.2

Safe to downgrade to: a release before 13.11.0

1. Check installed version

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

2. UPGRADE to 18.11.7 (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 13.11.0 (Debian / Ubuntu)

apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_13.11.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_13.11.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-6896?

gitlab: upgrade to 18.11.7, 19.0.4, 19.1.2. Exact commands for each OS are on this page.

Is CVE-2026-6896 being exploited?

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

CVE-2026-6896 affects gitlab. Severity is high (CVSS 8.7). GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with developer-role permissions

How urgent is CVE-2026-6896?

Priority 39/100. High severity

Software pages

GitLab vulnerabilities

Related CVEs

CVE-2026-85706 CRITICAL 10.0 EXPLOITED UPGRADE GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability

References

← Back to latest CVEs