Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Unrated

Improper Access Control in GitLab group packages API

IdentifiersCVE-2026-5796CWE-284

CVE-2026-5796 is an improper access control issue in GitLab CE/EE affecting all versions from 13.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. Due to incorrect authorization checks in the group packages feature, an authenticated user with Reporter-level permissions in a group could, under certain conditions, view package metadata belonging to projects where the Package Registry had been disabled. The flaw is in the group packages API / group packages functionality and results in exposure of package-related metadata despite the expected access restriction.

Share:
For your environment

Are you exposed to this one?

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.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows unauthorized disclosure of package metadata from projects that had the Package Registry disabled. Based on the provided information, this is an information exposure / access control bypass affecting metadata visibility rather than arbitrary code execution or direct package content modification. It weakens project-level security boundaries within a group by allowing a Reporter-level user to access information that should not be available through the group packages feature.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting Reporter-level group membership to trusted users and restricting access to groups containing projects where package metadata sensitivity matters. Review use of the group packages feature and minimize unnecessary package visibility across grouped projects. These are compensating controls only; the definitive mitigation is to upgrade to a remediated version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed version: 18.11.6 or later, 19.0.3 or later, or 19.1.1 or later, depending on the deployed release train. GitLab stated that self-managed customers should upgrade immediately. GitLab.com was already patched, and GitLab Dedicated customers required no action according to the provided context.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

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

4 SOURCESView more in app
What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-5796
NVD
nvd.nist.gov/vuln/detail/CVE-2026-5796
MITRE CWE · CWE-284
cwe.mitre.org