Description
GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries.
Published: 2026-07-29
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

GitLab Enterprise Edition has a vulnerability that allows sensitive data to be disclosed to an unintended host under certain conditions involving the handling of upstream requests in virtual registries. The flaw is rooted in improper credential protection, as identified by CWE‑522. If triggered, the exposure could reveal credentials or other confidential information to a malicious external system, thereby compromising confidentiality of the affected GitLab instance.

Affected Systems

The affected product is GitLab EE from version 18.8 up through the releases immediately preceding 19.0.5, 19.1.3 and 19.2.1. The recommended action is to upgrade to any of the patched releases – 19.0.5, 19.1.3, 19.2.1 or later – to eliminate the vulnerability.

Risk and Exploitability

This bug carries a CVSS score of 5.4, indicating a moderate level of impact. The EPSS score is below 1 %, suggesting a very low probability of exploitation at this time. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that exploitation would require an attacker to influence the upstream registry request flow, potentially by controlling an upstream service or manipulating registry configuration, so the attack vector is limited to scenarios where the GitLab instance processes external registry requests.

Generated by OpenCVE AI on August 2, 2026 at 07:43 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.0.5, 19.1.3, 19.2.1 or above.


OpenCVE Recommended Actions

  • Upgrade GitLab EE to version 19.0.5, 19.1.3, 19.2.1 or any later release to apply the vendor patch.
  • Restrict outbound connections from GitLab to only authorized registries, or enforce network segmentation to prevent accidental disclosure of credentials to unintended hosts.
  • Review virtual registry configurations and remove any unused or untrusted upstream registry references to minimize exposure risk.

Generated by OpenCVE AI on August 2, 2026 at 07:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 29 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 29 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Description GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries.
Title Insufficiently Protected Credentials in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-522
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-07-29T19:31:40.245Z

Reserved: 2026-07-22T11:33:42.887Z

Link: CVE-2026-16553

cve-icon Vulnrichment

Updated: 2026-07-29T19:31:36.346Z

cve-icon NVD

Status : Analyzed

Published: 2026-07-29T20:17:02.460

Modified: 2026-08-03T14:14:35.333

Link: CVE-2026-16553

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T07:45:03Z

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials