Is CVE-2026-101168 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101168 being exploited in the wild.

How severe is CVE-2026-101168?

Medium severity, with a CVSS score of 6.2, published 13 October 2026.

Which products and versions are affected?

GitLab Community Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1; GitLab Enterprise Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1.

Is there a fix for CVE-2026-101168?

Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101168 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-101168?

Check whether you run GitLab, GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101168: GitLab sensitive information exposure in Pages logs

CVE-2026-101168 · Severity: medium · CVSS 6.2 · Published 2026-10-13

GitLab Community and Enterprise Editions improperly logged sensitive information such as authentication tokens and secrets in GitLab Pages logs and error tracking. An authenticated user with access to Pages log data could extract these credentials to compromise other systems or accounts. The flaw affects versions from 12.0 onwards and has been patched.

Technologies: GitLab, GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-101168 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101168 being exploited in the wild.
How severe is CVE-2026-101168?: Medium severity, with a CVSS score of 6.2, published 13 October 2026.
Which products and versions are affected?: GitLab Community Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1; GitLab Enterprise Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1.
Is there a fix for CVE-2026-101168?: Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101168 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-101168?: Check whether you run GitLab, GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: GitLab CE/EE 19.2.8, 19.3.5, 19.4.2

Technical details

GitLab Pages failed to sanitize request data before writing it to log files and error tracking events, allowing secrets and access tokens to persist in plaintext. An authenticated attacker with access to Pages logs could retrieve these credentials. The vulnerability requires prior authentication and log access but poses a direct path to credential theft.

Affected products

GitLab GitLab Community Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1
GitLab GitLab Enterprise Edition 12.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1

Timeline

2026-10-13: disclosed
2026-10-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.