< ciso
brief />
Tag Banner

All news with #gitlab tag

34 articles

CISA Adds Actively Exploited Cisco and GitLab Flaws

πŸ›‘οΈ CISA has added two vulnerabilities affecting GitLab and Cisco products to its Known Exploited Vulnerabilities list, citing evidence of active exploitation. CVE-2026-97229 is a critical GitLab integer overflow that may allow unauthenticated remote code execution via crafted CI/CD regular expressions. CVE-2026-76418 impacts Cisco ASA/FTD and can cause device reloads and denial-of-service. Agencies are urged to apply patches by November 1, 2026.
read more β†’

Lessons from an intense Cybersecurity Black Week

πŸ›‘οΈ The week before October 25, 2026, saw a cascade of high‑impact security incidents, including PHP memory vulnerabilities (PHP2Shell), unpatched Linux kernel disclosures, a compromised LiteLLM PyPI release, a critical GitLab flaw, a Brotli/Node.js decoder bug (Node2Shell/HTTP2Shell), and a certificate authority compromise affecting Python trust bundles. Each incident required different remediation steps β€” emergency patches, containment and secret rotation, rebuilds from clean sources, or trust‑bundle updates β€” and highlighted challenges in prioritization, coordination, and distinguishing real risk from hype.
read more β†’

GitLab issues critical patches for unauthenticated code execution

πŸ”’ GitLab released patched CE and EE builds addressing a dozen vulnerabilities, including a critical integer overflow (CVE-2026-110264) that could permit unauthenticated code execution via a crafted regular expression. The updates also remediate a high-severity OmniAuth-to-LDAP auto-linking flaw (CVE-2026-15723) and several other issues; fixes were backported to multiple older releases. Administrators are urged to apply updates promptly due to the wide impact and potential need for downtime during database migrations.
read more β†’

GitLab warns of max-severity remote code execution

πŸ”’ GitLab released patches for a maximum-severity Regular Expression Compiler flaw (CVE-2026-110264) that could allow remote attackers to execute arbitrary code. Reported via HackerOne by researcher 'joaxcar', the issue stems from an integer overflow in the Regular Expression Compiler used to parse configuration files. Multiple CE and EE versions have been fixed and users are urged to upgrade immediately. Shadowserver reports thousands of exposed GitLab CE instances online.
read more β†’

Critical GitLab RCE Flaw Affects Releases Since 2014

πŸ”’ GitLab released patches on October 21 for a critical unauthenticated remote code execution bug (CVE-2026-110264) present in every self-managed release since 7.0. The fix supersedes an October 12 update that only covered 19.2+; instances updated then need the newer patch. GitLab.com and Dedicated tenants on recent internal builds are already protected, while self-managed administrators must upgrade to specified patched versions.
read more β†’

GitLab fixes critical regex RCE and several high-severity bugs

πŸ›‘οΈ GitLab released patches addressing a maximum-severity regular expression vulnerability (CVE-2026-97229) that could enable unauthenticated remote code execution, alongside fixes for five other high-severity issues affecting its CE and EE platforms. Administrators of self-managed installations are urged to upgrade to the corrected versions immediately; GitLab.com is already patched. The update also remedies flaws that could expose protected variables, allow unauthorized pipeline execution, enable XSS via repository content, and let attackers inject crafted content into AI agent instructions. Some fixes apply only to Enterprise Edition, and GitLab will publicly disclose full details 90 days after this release.
read more β†’

GitLab issues urgent patches for CVSS 10.0 flaw

πŸ”’ GitLab has released patches addressing a maximum-severity vulnerability that could permit unauthenticated arbitrary code execution via a crafted regular expression in CI/CD configurations, due to insufficient validation. The flaw, tracked as CVE-2026-97229 and rated CVSS 10.0, affects multiple 19.2–19.4 releases and is remediated in 19.4.2, 19.3.5, and 19.2.8. The advisory also fixes three high-severity issues impacting XSS, improper authorization in downstream pipeline creation, and a permissive regex allowing cache poisoning and exposure of protected variables.
read more β†’

GitLab issues emergency patch for RCE in regex engine

πŸ”’ GitLab warned users to immediately patch a maximum-severity remote code execution flaw in its CI/CD Regular Expression Compiler, tracked as CVE-2026-97229. Discovered by researcher 'joaxcar' via GitLab's HackerOne program, the issue is an integer overflow during regex parsing that could enable unauthenticated arbitrary code execution. Fixed releases for CE and EE span versions before 19.2.8, 19.3.4, and 19.4.2, and GitLab urges immediate upgrades while noting GitLab.com is already patched.
read more β†’

GitLab patches critical AI Gateway remote command flaw

πŸ”’ GitLab disclosed a critical vulnerability (CVE-2026-90970) in its AI Gateway that could let a logged-in user with Duo Agent Platform access escape a prompt template sandbox and run commands on self-hosted gateways. The flaw, rated 9.9 CVSS, affects gateway releases from 18.1.6 through the 19.1 line and is fixed in 19.2.4, 19.3.2, and 19.4.1. GitLab has already remediated gateways it hosts; self-managed customers are urged to update immediately.
read more β†’

GitLab warns of critical RCE in AI Gateway

πŸ”” GitLab warned customers to immediately patch a critical AI Gateway vulnerability that could allow attackers to execute arbitrary commands on vulnerable instances. The flaw, tracked as CVE-2026-90970, affects self-hosted AI Gateway deployments and stems from improper neutralization allowing sandbox escape by authenticated users with Duo Agent Platform access. GitLab released versions 19.2.4, 19.3.2, and 19.4.1 to address the issue and said hosted AI Gateway users are already protected.
read more β†’

GitLab issue-email token exposes account access

πŸ›‘οΈ A GitLab feature that supplies a project-scoped email address to create issues embeds a long-lived token in the address, which can be used to act as the linked user across projects. Aikido Security found the token (prefixed with glimt-) is identical across project addresses for an account and bypasses IP restrictions, enabling actions like creating issues and merge requests with the account's permissions. GitLab updated wording to acknowledge merge request capabilities; Aikido recommends treating the addresses as credentials and rotating tokens if exposed.
read more β†’

Exposed GitLab email tokens enable malicious pushes

πŸ“§ Researchers found that private GitLab incoming-email addresses, generated by the Email work item to this project feature, are being published in public READMEs and guides. These addresses include long-lived tokens that let anyone create issues or merge requests if they modify the address suffix, potentially bypassing IP restrictions. Aikido reported instances affecting popular open-source projects and urges token resets and removal from public docs.
read more β†’

Leaked GitLab email token enables commits and CI

πŸ“§ GitLab issues each user a persistent incoming-email address for filing work items; that address contains a token tied to the account and does not expire. Researchers at Aikido Security found the token is shared across a user's project addresses and allows anyone who holds the address to create issues, open merge requests by email, commit patches to branches (including main) and trigger CI/CD jobs that run as the account holder. GitLab currently does not verify the sender address, and incoming email bypasses IP allowlists and two-factor requirements.
read more β†’

Maximum-severity GitLab flaw risks CI/CD trust

🚨 GitLab disclosed CVE-2026-85706, a maximum-severity path traversal flaw in its repository commits API that can allow unauthenticated attackers to read arbitrary files with a single HTTP request. The bug affected Community and Enterprise editions and has been patched; GitLab urged self-hosted, public-facing instances to patch immediately or remove access. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog, and threat intel already reports in-the-wild probes. Experts warn this poses broad risk because GitLab often links to build, deployment, and secret-bearing files.
read more β†’

Urgent Patch for GitLab Path Traversal Flaw

πŸ›‘οΈ GitLab has released a fix for a maximum-severity path traversal vulnerability (CVE-2026-85706) that allowed unauthenticated users to read arbitrary files via the repository commits API. The issue affects multiple versions and was remediated on September 10. Security vendors reported in-the-wild probes shortly after disclosure, and CISA added the flaw to its KEV Catalog, urging rapid remediation. Organizations are advised to patch immediately and hunt logs for suspicious POST requests to the commits endpoint.
read more β†’

Critical GitLab path traversal flaw draws rapid probes

πŸ”’ GitLab released emergency patches to fix multiple vulnerabilities, including CVE-2026-85706, a CVSS 10.0 path traversal bug in the repository commits API that can let unauthenticated actors read arbitrary files under certain conditions. The flaw affects several CE and EE releases prior to the 19.3.2, 19.2.6 and 19.1.8 fixes, and was observed being probed in the wild from 06:00 UTC on September 11, 2026. GitLab also patched an insecure deserialization issue in EE (CVE-2026-87719, CVSS 9.9). Organizations running internet-exposed, self-managed instances are urged to apply patches immediately or restrict public access.
read more β†’

GitLab urges immediate patch for critical path flaw

🚨 GitLab has released urgent updates to address a maximum-severity path traversal vulnerability (CVE-2026-85706) discovered in the repository commits API and reported via HackerOne. The flaw allows unauthenticated attackers, under certain conditions, to read arbitrary files from vulnerable servers, potentially exposing credentials and secrets. GitLab patched this and a separate critical insecure deserialization bug (CVE-2026-87719) and strongly urges self-managed instances to upgrade to the fixed CE/EE releases immediately.
read more β†’

GitLab critical code injection exploited rapidly

πŸ›‘οΈ A critical GitLab vulnerability, CVE-2026-19478 (CVSS 9.4), enables unauthenticated code injection allowing modification or deletion of public projects under certain conditions. Affected CE and EE versions include 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4. GitLab released fixes in patched releases, while watchTowr reports rapid in-the-wild exploitation and reproduction using probes targeting GraphQL directives.
read more β†’

Critical GitLab vulnerability allows repo deletion

πŸ”’ GitLab patched a critical code-injection vulnerability in its GraphQL directive that could let unauthenticated attackers modify or delete repositories with a single HTTP request. The update also fixes a high-risk CSRF flaw in the GraphQL multiplex handler. GitLab released multiple patched CE and EE versions and advises administrators to restrict access to /api/graphql and make repos private until updates are applied.
read more β†’

Critical GitLab GraphQL Flaw Allows Remote Project Changes

πŸ”’ GitLab released out-of-cycle security updates on August 17, 2026, to fix a critical GraphQL vulnerability (CVE-2026-19478) that could let unauthenticated attackers remotely modify or delete public projects and user data. The patches apply to self-managed instances in versions 18.11.11, 19.0.8, 19.1.6, and 19.2.4; hosted GitLab.com and Dedicated are already patched. A second, High-severity issue (CVE-2026-19650) addresses a CSRF-related GraphQL multiplex handling flaw requiring user interaction.
read more β†’