Skip to main content
Mallory
MediumVulnerability

CVE-2026-104717: Missing Authorization in GitLab EE Group Iterations

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
CVSS4.3Medium · v3.1
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-104717CWE-862 · Missing Authorization

A missing authorization vulnerability in GitLab Enterprise Edition allows an authenticated user, under certain conditions, to view iteration details belonging to private groups they are not authorized to access. Affected versions are 13.4 through versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The vulnerability exposes private group information without granting membership or authorized access to those groups.

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.

Unauthorized disclosure of private groups' iteration details, resulting in limited confidentiality loss. No integrity or availability impact is identified. The vulnerability has a CVSS v3.1 base score of 4.3 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.

Mitigation

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

No temporary workaround is specified. Apply the fixed release to address the missing authorization checks.

Remediation

Patch, then assume compromise.

Upgrade affected GitLab EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch, or a later fixed release. 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-104717 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-104717 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-104717?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-104717.
Is there a patch for CVE-2026-104717?
Upgrade affected GitLab EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch, or a later fixed release. Affected self-managed installations should be upgraded immediately.
How severe is CVE-2026-104717?
CVE-2026-104717 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.20% (10th 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.