dbcve.org
GitLabApplication

CVE-2026-16553

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-29
Fix available
A fix is available. Upgrade to 19.0.5 / 19.1.3 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-522

Credentials are stored or transmitted without adequate protection, so an attacker who reaches them can reuse them directly. One weak link here can unravel an entire system. Remediation means strong hashing for stored secrets, encryption in transit, and never writing credentials to logs.

General guidance for the insufficiently protected credentials class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 18.8.0, < 19.0.5>= 19.1.0, < 19.1.3= 19.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 19.0.5 / 19.1.3 or later
Fixed in 19.0.519.1.3
Recommended fix High confidence

Upgrade to GitLab 19.0.5, 19.1.3, 19.2.1, or later (EE editions)

  1. 1. Identify the currently installed GitLab EE version using `gitlab-rake gitlab:env:info` or checking the GitLab admin dashboard
  2. 2. Based on the current version, determine the appropriate upgrade target: if running 18.8.x, upgrade to 19.0.5 or later; if running 19.1.x, upgrade to 19.1.3 or later; if running 19.2.x, upgrade to 19.2.1 or later
  3. 3. Review the GitLab upgrade documentation at docs.gitlab.com for the specific upgrade path to your target version
  4. 4. Create a full backup of the GitLab instance before upgrading using `gitlab-backup create`
  5. 5. Stop GitLab services with `gitlab-ctl stop`
  6. 6. Update the GitLab package using the appropriate method for your installation (omnibus package or source)
  7. 7. Reconfigure GitLab with `gitlab-ctl reconfigure`
  8. 8. Restart GitLab services with `gitlab-ctl start`
Caveat Standard GitLab version upgrades may include database migrations; review release notes for any known breaking changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-16553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-16553 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data