Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-96893: GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.2.8, 19.3 before 19.3.5

37
Routine
HIGH 7.3UPGRADE

CVE-2026-96893 is a high-severity flaw (CVSS 7.3) 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.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to inject specially crafted content into AI agent instructions, potentially causing unintended command execution attributed to other users, due to improper neutralization of special elements in AI conversation context construction.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.3 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-74
Published2026-10-13
Last modified2026-10-14
Publisher (CNA): GitLab Inc. · Vendor: gitlab

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

gitlab gitlab UPGRADE
Affected: >= 19.1.0 and < 19.2.8 · >= 19.3.0 and < 19.3.5 · >= 19.4.0 and < 19.4.2
Fixed in: 19.2.8, 19.3.5, 19.4.2
Safe to downgrade to: a release before 19.1.0
1. Check installed version
apt-cache policy gitlab || rpm -q gitlab || gitlab --version
2. UPGRADE to 19.2.8 (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.1.0 (Debian / Ubuntu)
apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_19.1.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.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.
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-96893?

gitlab: upgrade to 19.2.8, 19.3.5, 19.4.2. Exact commands for each OS are on this page.

Is CVE-2026-96893 being exploited?

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

CVE-2026-96893 affects gitlab. Severity is high (CVSS 7.3). GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to inject specially crafted cont

How urgent is CVE-2026-96893?

Priority 37/100. High severity

Software pages

GitLab vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.