Loading story…
GitLab released security updates for Community Edition and Enterprise Edition in versions 16.6.1, 16.5.3, and 16.4.3, urging affected self-managed installations to upgrade immediately. The fixes addressed multiple vulnerabilities spanning XSS, privilege escalation, information disclosure, authorization bypass, package registry access issues, protected branch and pipeline schedule permission bypasses, and client-side denial of service. The most severe issue was CVE-2023-6033, a high-severity cross-site scripting flaw in Jira integration configuration, while GitLab said GitLab.com was already running the patched version.
One of the patched Enterprise Edition issues, CVE-2023-4658, was an incorrect authorization flaw that allowed a guest user to abuse the "Allowed to merge" permission when that right was inherited through a group. GitLab rated that bug CVSS 3.1 / Low and said it affected versions from 8.13 before 16.4.3, 16.5 before 16.5.3, and 16.6 before 16.6.1. The release also included fixes for unauthorized access to release descriptions and other EE-specific authorization weaknesses, along with bundled component updates for Mattermost, PostgreSQL, and pcre2.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
The CVE record states that CVE-2023-4658, an incorrect authorization flaw in GitLab EE involving the "Allowed to merge" permission granted through a group, was published on 2023-12-01. The record attributes the report to theluci through GitLab's HackerOne bug bounty program.
On 2023-11-30, GitLab released security updates for Community Edition and Enterprise Edition in versions 16.6.1, 16.5.3, and 16.4.3, fixing multiple vulnerabilities including CVE-2023-6033 and several authorization and privilege issues. GitLab urged affected installations to upgrade immediately and said GitLab.com was already running the patched version.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
GitLab released patched Community Edition and Enterprise Edition versions **17.0.1**, **16.11.3**, and **16.10.6** to fix multiple security vulnerabilities and bug issues, and urged self-managed customers to upgrade immediately. The most severe issue was a high-severity cross-site scripting flaw in the Web IDE that could enable **one-click account takeover**, alongside additional medium-severity weaknesses affecting denial of service, CSRF protections, authorization controls, and information disclosure. The release is associated with several tracked vulnerabilities, including **`CVE-2024-5258`**, **`CVE-2023-7045`**, **`CVE-2024-4835`**, and **`CVE-2024-2874`**. GitLab said **GitLab.com** was already running the patched version when the advisory was published, and the notice also referenced mitigations related to a **PDF.js** vulnerability and an update for **Mattermost** as part of the broader security response.
Jul 24, 2026
GitLab released security updates for self-managed GitLab Community Edition and Enterprise Edition, publishing versions **17.9.1**, **17.8.4**, and **17.7.6** to fix five vulnerabilities and urging administrators to upgrade immediately. The issues include two high-severity cross-site scripting flaws tracked as **`CVE-2025-0475`** and **`CVE-2025-0555`**, along with three medium-severity authorization or injection weaknesses identified as **`CVE-2024-8186`**, **`CVE-2024-10925`**, and **`CVE-2025-0307`**. GitLab said **GitLab.com** was already running the patched version and that **GitLab Dedicated** customers did not need to take action, leaving self-managed deployments as the primary exposure point. The fixes apply across multiple supported release lines, and the vendor framed the update as an urgent security patch cycle for affected CE and EE installations.
Jul 24, 2026
GitLab released **19.0.2**, **18.11.5**, and **18.10.8** for self-managed Community Edition and Enterprise Edition deployments to fix **11 security vulnerabilities** and additional bugs, and urged administrators to upgrade immediately. The advisory says all versions before those releases are affected, while **GitLab.com** has already been patched and **GitLab Dedicated** customers do not need to take action. GitLab also warned that the update includes database migrations that may cause downtime on single-node instances, though multi-node environments can use zero-downtime upgrade procedures. The most severe issue, **`CVE-2026-6552`** (**CVSS 8.7**), is an improper authorization flaw in GitLab EE's Group SAML identity management that could let an authenticated **group Owner** take over another group member's account under certain conditions. GitLab also fixed **`CVE-2026-10087`**, an Analytics Dashboard cross-site scripting flaw in GitLab EE that could allow an authenticated **developer** to execute arbitrary client-side code in a victim's browser. The broader patch set addresses additional risks including denial of service in Grape API JSON parsing, SSRF, unauthorized access to confidential data, and other authorization bypasses, and government and vendor advisories have called on organizations to apply the patched versions.
Jul 25, 2026