Skip to main content
Mallory
MediumVulnerability

CVE-2026-16545: Unauthenticated Private Project Metadata Disclosure in GitLab Package Registry

Published Nov 17, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS5.3Medium · v3.1
EPSS0.27%20th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-16545CWE-863 · Incorrect Authorization

CVE-2026-16545 is an incorrect authorization vulnerability in the GitLab Community Edition and Enterprise Edition Package Registry. Under certain conditions, incorrect authorization checks allow unauthenticated users to read private project metadata through packages published by other projects. Affected versions are 12.10 through versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation exposes private project metadata to unauthenticated remote attackers. The vulnerability has a CVSS v3.1 score of 5.3, reflecting low confidentiality impact with no identified integrity or availability impact. It does not establish access to private repository contents or code execution.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary workaround is documented. Apply a fixed release rather than relying on an unverified workaround.

Remediation

Patch, then assume compromise.

Upgrade affected GitLab CE/EE installations to 19.3.9, 19.4.8, 19.5.6, or a later fixed release, as appropriate for the release branch. Affected self-managed installations should be upgraded immediately. GitLab.com is already patched, and GitLab Dedicated customers require no action.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-16545 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-16545 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-16545?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-16545.
Is there a patch for CVE-2026-16545?
Upgrade affected GitLab CE/EE installations to 19.3.9, 19.4.8, 19.5.6, or a later fixed release, as appropriate for the release branch. Affected self-managed installations should be upgraded immediately.
How severe is CVE-2026-16545?
CVE-2026-16545 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.27% (20th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.