ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Product

GitLab

2 mentions in 7 days · 6 in 30 days · 6 total · first seen · last

Search everything

Timeline

GitLab security advisory (AV26-917)

Canada's Cyber Centre warns GitLab versions before 19.1.8, 19.2.6 and 19.3.2 are affected; CISA added CVE-2026-85706 to KEV.

The Canadian Centre for Cyber Security issued advisory AV26-917 on September 11, 2026, warning that GitLab versions prior to 19.1.8, 19.2.6, and 19.3.2 are affected by vulnerabilities. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog on the same date. The Cyber Centre urges users and administrators to review the advisory links and apply GitLab's critical patch release updates.

Canadian Centre for Cyber Securityupdated · 21h agofirst · 4d agoAdvisory in the wild 17 sourcesCVE-2026-85706

OpenAI Builds ‘Defense Factory’ Where AI Agents Continuously Find and Fix Vulnerabilities

OpenAI unveils a Defense Factory where AI agents continuously discover, validate, and fix vulnerabilities, integrating GitHub, Snyk, Semgrep, Tenable, and ServiceNow.

OpenAI introduced a Defense Factory, an agent-first cybersecurity operation that connects AI agents to developer and security tools via APIs, CLIs, and Model Context Protocol integrations including GitHub, GitLab, Snyk, Semgrep, Tenable, Jira, Linear, and ServiceNow. During an internal security sprint, over 250 people across more than 100 service areas closed 53 urgent or high-priority issues on day one, achieved a 90.6% accepted ownership-assignment rate, and Codex generated all remediation patches with only 0.53% rolled back. Agent-assisted deduplication flagged 37% of findings as duplicates, and runtime validation reproduced 19.5% of findings, cutting the false-positive rate to 0.81%. OpenAI argues defenders must exploit a temporary 'defender's window' using source-code access and frontier models before open-weight models enable autonomous offensive agent fleets.

Cyber Security News · 5d agoTools 4 sources

How Virginia Tech Connected Pentesting to Its Engineering Workflow

Horizon3.ai customer story details Virginia Tech automating external pentesting via NodeZero's GraphQL API with GitLab and ServiceNow integration for remediation tracking.

Horizon3.ai published a customer story describing how Virginia Tech, whose environment serves more than 38,000 students across hundreds of independent departments and multiple cloud providers, used NodeZero's GraphQL API to automate external pentesting through GitLab. Findings are routed directly into ServiceNow for subnet-owner assignment and remediation tracking, creating a repeatable attack-validation-to-remediation workflow.

Horizon3.ai · 12d agoIndustry1

Version Control DFIR: a Cheatsheet to GitHub, GitLab, Bitbucket, and Azure DevOps

Wiz published a DFIR cheatsheet covering log visibility, incident readiness, and threat hunting across GitHub, GitLab, Bitbucket, and Azure DevOps.

Wiz researchers released a practitioner's guide to version control system forensics, incident response, and threat hunting. The cheatsheet maps log sources, audit capabilities, and hunting workflows across GitHub, GitLab, Bitbucket, and Azure DevOps. It aims to improve incident readiness for source code and CI/CD compromise scenarios.

Wiz Blog · 19d agoResearch1

GitLab Warns of Active Exploitation of Critical GraphQL Flaw

GitLab emergency-patches actively exploited flaw CVE-2026-19478 (CVSS 9.4), letting unauthenticated attackers modify or delete public projects on self-managed servers.

GitLab emergency-patched CVE-2026-19478 (CVSS 9.4) on August 17 after WatchTowr researchers warned of active exploitation. The flaw lets unauthenticated attackers remotely modify or delete public projects and user data through a GraphQL directive, affecting only self-managed installations. Fixes ship in versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11; the 18.2-18.10 branches receive no patch and must upgrade. Until patching, defenders should restrict unauthenticated access to /api/graphql, disable public repositories, and hunt for @gl_introduced in logs.

Security Affairs · 23d agoExploit / PoC in the wildCVE-2026-194781

GitLab Patches Critical Unauthenticated GraphQL Vulnerability

GitLab issued an emergency patch for a critical unauthenticated GraphQL flaw (CVE-2026-19478, CVSS 9.4) enabling remote modification or deletion of public projects.

GitLab patched CVE-2026-19478 (CVSS 9.4), an unauthenticated GraphQL directive flaw allowing remote modification or deletion of public projects and user data on self-managed servers. The emergency patch released August 17 covers versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11, but no fixes exist for the 18.2-18.10 branches. A second issue, a CSRF weakness in GraphQL multiplex queries (CVE-2026-19650, CVSS 7.1), shipped in the same release. No exploitation or public PoC has been observed; the flaw was reported by hiimguardian through HackerOne.

Security Affairs · 28d agoVulnerabilityCVE-2026-19478CVE-2026-196501

Related CVEs

  • CVE-2026-194789.16%
    Unauthenticated GraphQL Code Injection in GitLab CE/EE Enables Data Tampering
    GitLab has patched a critical (CVSS 9.1) code injection flaw (CWE-94) in how GitLab Community Edition (CE) and Enterprise Edition (EE) process GraphQL directives. Under certain conditions, an unauthenticated remote attacker can abuse a GraphQL directive to modify or delete public projects and user data on affected instances, requiring no privileges or user interaction; the impact is to integrity and availability, not confidentiality. Affected versions span all GitLab CE/EE releases from 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, which covers self-managed installations as well as the same codebase that powers the GitLab.com SaaS. News reports indicate the flaw came under active exploitation within days of disclosure, and EPSS assigns a 5.8% probability of exploitation within 30 days (93rd percentile). It is not yet listed in CISA's KEV catalog and no public proof-of-concept is known, but defenders should treat it as an actively exploited, unauthenticated, high-impact issue.
    · GitLab CE all versions from 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 EE all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4mass
  • CVE-2026-8570610.012%
    Unauthenticated Path Traversal Arbitrary File Read in GitLab CE/EE
    CVE-2026-85706 is a path traversal flaw (CWE-35) in GitLab Community Edition and Enterprise Edition in which the repository commits API does not properly confine file paths and does not enforce authentication, allowing an unauthenticated attacker to read arbitrary files from the GitLab server. It is triggered by sending a crafted unauthenticated request to the commits API that supplies traversal sequences moving outside the intended repository path. An attacker gains the ability to read arbitrary files on the host, which can expose configuration files, certificates, and stored credentials or keys; related reporting on the recent GitLab patch wave also notes credential theft and code execution flaws, though this CVE itself is the file-read issue. All self-managed GitLab CE and EE deployments are in scope, and CISA did not publish specific affected version ranges in this data. The flaw was added to CISA's KEV catalog on 2026-09-11 and is being actively probed and exploited in the wild within a day of disclosure, with three public proof-of-concept repositories available; ransomware use is not yet confirmed.
    · GitLab Community Edition · GitLab Enterprise Edition KEV PoC ×9mass
  • CVE-2026-196507.1<1%
    CSRF Flaw in GitLab CE/EE GraphQL Lets GET Requests Execute Mutations
    GitLab CE/EE contains an improper request-validation flaw (CWE-352, CSRF) in GraphQL multiplex query handling that, under certain conditions, allowed mutations to be executed via GET requests, which should normally only carry queries. An unauthenticated attacker can exploit this by inducing GET requests against a vulnerable instance's GraphQL endpoint; the CVSS user-interaction requirement indicates a logged-in user's browser is typically the vehicle, and no credentials or privileges are needed by the attacker. Successful exploitation carries no confidentiality impact but a high integrity impact and low availability impact (CVSS 7.1), meaning attackers could modify data and potentially delete resources such as project content. All self-managed GitLab CE/EE deployments running affected trains (18.2 through 18.11.10, 19.0 through 19.0.7, 19.1 through 19.1.5, or 19.2 through 19.2.3) are exposed; related coverage notes GitLab's same patch release also fixed a companion critical GraphQL flaw (CVE-2026-19478) letting attackers modify or delete public projects. There is no known in-the-wild exploitation, public proof-of-concept, or KEV listing, and EPSS assigns only a 0.5% probability of exploitation within 30 days.
    · GitLab CE/EE (Community Edition and Enterprise Edition) all versions from 18.2 before 18.11.11; 19.0 before 19.0.8; 19.1 before 19.1.6; 19.2 before 19.2.4large

Appears with

vendor GitLab 3product GitHub 2product ServiceNow 2organization OpenAI 1organization WatchTowr 1organization Wiz 1product Azure DevOps 1product Bitbucket 1product Codex 1product Jira 1product Linear 1product Model Context Protocol 1product NodeZero 1product Semgrep 1product Snyk 1product Tenable 1
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.