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… (CVE-2026-16553)
A vulnerability in GitLab Enterprise Edition versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow sensitive information disclosure due to improper handling of upstream requests in virtual registries. This issue has been remediated by GitLab in the specified fixed versions. The vulnerability is classified as CWE-522 and has a CVSS 3.1 vector indicating network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, limited confidentiality impact, no integrity impact, and low availability impact. No known exploits in the wild have been reported.
AI Analysis
Technical Summary
CVE-2026-16553 is a vulnerability in GitLab EE affecting versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Under certain conditions, it could lead to disclosure of sensitive information to unintended hosts because of improper handling of upstream requests in virtual registries. The issue has been fixed in GitLab EE versions 19.0.5, 19.1.3, and 19.2.1. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L) reflects a network attack vector with low complexity and limited confidentiality impact. No public exploits are known.
Potential Impact
The vulnerability could allow an attacker with low privileges to cause some sensitive information to be disclosed to an unintended host. The impact is limited to confidentiality with no integrity or significant availability impact. There are no known exploits in the wild.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 19.0.5, 19.1.3, and 19.2.1. Users should upgrade affected GitLab EE instances to these versions or later to remediate the issue. Patch status is confirmed by the vendor advisory embedded in the 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… (CVE-2026-16553)
Description
A vulnerability in GitLab Enterprise Edition versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow sensitive information disclosure due to improper handling of upstream requests in virtual registries. This issue has been remediated by GitLab in the specified fixed versions. The vulnerability is classified as CWE-522 and has a CVSS 3.1 vector indicating network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, limited confidentiality impact, no integrity impact, and low availability impact. No known exploits in the wild have been reported.
CVSS v3.1
Score 5.4medium
Affected software
pkg:github/gitlab-org/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16553 is a vulnerability in GitLab EE affecting versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Under certain conditions, it could lead to disclosure of sensitive information to unintended hosts because of improper handling of upstream requests in virtual registries. The issue has been fixed in GitLab EE versions 19.0.5, 19.1.3, and 19.2.1. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L) reflects a network attack vector with low complexity and limited confidentiality impact. No public exploits are known.
Potential Impact
The vulnerability could allow an attacker with low privileges to cause some sensitive information to be disclosed to an unintended host. The impact is limited to confidentiality with no integrity or significant availability impact. There are no known exploits in the wild.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 19.0.5, 19.1.3, and 19.2.1. Users should upgrade affected GitLab EE instances to these versions or later to remediate the issue. Patch status is confirmed by the vendor advisory embedded in the description.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5c98-v836-vg79
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-16553"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6ae5339c2644c7f89866d9
Added to database: 07/30/2026, 05:46:27 UTC
Last enriched: 07/30/2026, 07:04:21 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.