CVE-2026-101168 Insertion of Sensitive Information into Log File in GitLab

Medium 6.2 Published Updated

Authenticated users with log access can obtain access tokens and secrets due to sensitive data being logged in GitLab.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-101168?

CVE-2026-101168 is a medium-severity vulnerability in Gitlab Gitlab, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.0 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 with access to GitLab Pages log data to obtain access tokens and other secrets, due to insertion of sensitive request data into log files and error tracking events.

Weakness: CWE-532

Which versions are affected by CVE-2026-101168?

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

PackageAffectedFixed in
gitlab BitnamiFrom 12.0.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-101168?

Upgrade gitlab to a fixed version for your release line: 19.2.8, 19.3.5 or 19.4.2.

Is CVE-2026-101168 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-101168, GHSA-v4pv-wcvf-gwvm, MINI-2788-qxj5-6jjc, MINI-29jr-hr4p-4vqh, MINI-3cxr-325x-cx4c, MINI-3m9r-7w2f-q7xm and 48 more.

Is CVE-2026-101168 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free