Loading vulnerability…
CVE-2026-16553 is a medium-severity information disclosure vulnerability in GitLab Enterprise Edition Virtual Registries. Affected versions are all releases from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. The flaw is caused by improper handling of upstream requests in virtual registries, which under certain conditions could result in sensitive information being disclosed to an unintended host. The issue is described as an insufficiently protected credentials problem in Virtual Registries, indicating that request handling could expose credential or other sensitive request-associated data during communication with upstream registry endpoints.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity credential protection flaw affecting GitLab Virtual Registries.
An information disclosure vulnerability in GitLab EE Virtual Registries that could expose sensitive information to an unintended host due to improper handling of upstream requests.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.