Loading story…
GitLab released 19.1.2, 19.0.4, and 18.11.7 to fix eight security vulnerabilities in GitLab Community Edition and Enterprise Edition, including two high-severity script-injection issues. One of the disclosed flaws, CVE-2026-6896, is a CWE-79 cross-site scripting vulnerability in GitLab EE that could let an authenticated user with Developer privileges execute arbitrary script in another user’s browser under certain conditions. The issue affects releases from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2.
The patch set also addresses a medium-severity credential exposure issue and several authorization and access-control weaknesses. GitLab said GitLab.com was already patched and GitLab Dedicated customers do not need to take action, but urged operators of self-managed instances on affected versions to upgrade immediately. The release includes database migrations that may cause downtime on single-node deployments, while multi-node environments can avoid interruption by following GitLab’s zero-downtime upgrade procedures.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
GitLab's July 8, 2026 security release was described as fixing eight vulnerabilities across Community Edition and Enterprise Edition, including CVE-2026-13320, an HTML injection flaw, plus issues involving repository mirroring credential exposure, private project metadata leakage, project existence inference, authorization weaknesses, and Git reference ambiguity. GitLab also said GitLab Dedicated customers were unaffected and that fuller disclosures would follow after 90 days.
CVE-2026-6896 was disclosed as an improper neutralization of input during web page generation issue in GitLab EE that could let an authenticated user with developer-role permissions execute arbitrary scripts in another user's browser under certain conditions. The issue affects releases from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2, and GitLab remediated it in the fixed releases.
On 2026-07-08, GitLab released versions 19.1.2, 19.0.4, and 18.11.7 for Community Edition and Enterprise Edition to fix multiple security vulnerabilities and bug fixes. GitLab said GitLab.com was already patched and advised self-managed customers to upgrade immediately.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourcecvefeed.io
Open sourcedocs.gitlab.com
Open sourceMap 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 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 issued emergency security updates for self-managed Community Edition and Enterprise Edition instances to fix multiple high-severity vulnerabilities, including several cross-site scripting (**XSS**) flaws and unauthenticated denial-of-service (**DoS**) issues. The XSS bugs could allow attackers to run malicious JavaScript in users’ browsers, potentially leading to session hijacking, token theft, and repository manipulation, while the DoS flaws could disrupt CI/CD pipelines and broader workflow operations. The affected products are GitLab CE and EE versions earlier than `18.11.3`, `18.10.6`, and `18.9.7`, and administrators were urged to review GitLab’s release guidance and upgrade immediately to those patched versions. GitLab said its cloud-hosted platforms had already been remediated, while self-hosted operators were warned that single-node upgrades require downtime because of database migrations, whereas multi-node deployments can follow standard zero-downtime upgrade procedures.
Jun 29, 2026
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