CVE-2026-3848 Improper Neutralization of CRLF Sequences ('CRLF Injection') in GitLab

Medium 5.0 Published 11 Mar 2026 Updated 12 Mar 2026

Authenticated users can trigger unintended internal requests via proxy environments due to CRLF injection in GitLab's import functionality.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-3848?

CVE-2026-3848 is a medium-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.11 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to make unintended internal requests through proxy environments under certain conditions due to improper input validation in import functionality.

Weakness: CWE-93

Which versions are affected by CVE-2026-3848?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `8.11.0`	`18.7.6, 18.8.6, 18.9.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-3848?

Upgrade gitlab to a fixed version for your release line: 18.7.6, 18.8.6 or 18.9.2.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-3848 being exploited?

There is no known exploitation of CVE-2026-3848 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-3848, GHSA-j592-x6jp-9fg8, UBUNTU-CVE-2026-3848.