CVE-2026-3855 Improper Control of Resource Identifiers ('Resource Injection') in GitLab

Low 3.1 Published 16 Sep 2026 Updated 16 Sep 2026

Authenticated users with project permissions can access restricted server files or cause denial of service via improper validation in Terraform state uploads.

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

CVE-2026-3855 is a low-severity path traversal vulnerability in Gitlab Gitlab, published on 16 Sep 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 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user with project-level permissions to access restricted file contents on the server or cause denial of service due to improper validation of parameters in the Terraform state upload functionality.

Weakness: CWE-99

Which versions are affected by CVE-2026-3855?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `18.2.7`	`19.1.8, 19.2.6, 19.3.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-3855?

Upgrade gitlab to a fixed version for your release line: 19.1.8, 19.2.6 or 19.3.2.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-3855 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-3855, GHSA-74fm-x674-6p6m, MINI-fcgr-w2jh-g99q, MINI-h544-76f3-77f2, MINI-qhhg-3mqj-h5jq.