Is CVE-2026-105777 exploited in the wild?

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

How severe is CVE-2026-105777?

Medium severity, with a CVSS score of 4.3, published 22 October 2026.

Which products and versions are affected?

GitLab Community Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Is there a fix for CVE-2026-105777?

Yes: fixed in GitLab CE/EE 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-105777 attacked?

It is attacked over the network.

Am I affected by CVE-2026-105777?

Check whether you run 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-105777: GitLab CE/EE internal credential exposure in response headers

CVE-2026-105777 · Severity: medium · CVSS 4.3 · Published 2026-10-22

GitLab is a web-based code repository and collaboration platform used by development teams. An unauthenticated attacker could retrieve sensitive internal server credentials from HTTP response headers due to improper filtering. This could allow an attacker to gain unauthorized access to internal systems or escalate privileges.

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

Quick answers

Is CVE-2026-105777 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105777 being exploited in the wild.
How severe is CVE-2026-105777?: Medium severity, with a CVSS score of 4.3, published 22 October 2026.
Which products and versions are affected?: GitLab Community Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.
Is there a fix for CVE-2026-105777?: Yes: fixed in GitLab CE/EE 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105777 attacked?: It is attacked over the network.
Am I affected by CVE-2026-105777?: Check whether you run 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 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1

Technical details

The vulnerability stems from improper filtering of internal response headers in GitLab CE/EE, allowing unauthenticated users to retrieve sensitive server credentials under certain conditions. The attack requires only network access to the GitLab instance with no authentication or user interaction needed. An attacker could extract credentials from HTTP responses and use them to further compromise the GitLab infrastructure.

Affected products

GitLab Community Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1
GitLab Enterprise Edition 17.6.5 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1

Timeline

2026-10-22: disclosed
2026-10-21: patched

References

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