GitLab up to 19.2.7/19.3.4/19.4.1 Kubernetes Proxy redirect

Summaryinfo

A vulnerability classified as problematic has been found in GitLab up to 19.2.7/19.3.4/19.4.1. Affected by this issue is some unknown functionality of the component Kubernetes Proxy. This manipulation causes redirect. This vulnerability is handled as CVE-2026-7767. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in GitLab up to 19.2.7/19.3.4/19.4.1 and classified as problematic. Affected by this vulnerability is some unknown processing of the component Kubernetes Proxy. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect integrity. The summary by CVE is:

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.11 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 controlling a Kubernetes agent to cause sensitive authentication tokens to be sent to an unintended server due to improper redirect validation in the Kubernetes proxy.

It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2026-7767 since 05/04/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.

Upgrading to version 19.2.8, 19.3.5 or 19.4.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-3858). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Red Hat Enterprise Linux
• Open Source GitLab

Productinfo

Type

• Bug Tracking Software

Name

• GitLab

Version

• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.2.6
• 19.2.7
• 19.3.0
• 19.3.1
• 19.3.2
• 19.3.3
• 19.3.4
• 19.4.0
• 19.4.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion