ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Product

Advanced Search

1 mentions in 7 days · 1 in 30 days · 1 total · first seen · last

Search everything

Timeline

GitLab’s critical flaw is already drawing internet-wide probes

GitLab patches two critical flaws (CVE-2026-85706 CVSS 10.0, CVE-2026-87719) as WatchTowr observes internet-wide probing of the unauthenticated file-read bug.

GitLab released emergency patches for two high-severity flaws in Community and Enterprise Editions, urging self-managed operators to upgrade immediately while saying its hosted and Dedicated offerings are fixed or unaffected. CVE-2026-85706 (CVSS 10.0) is a path traversal in the repository commits interface that lets unauthenticated attackers read any file on the server and affects releases 18.7 through 19.1.8 plus the 19.2 and 19.3 lines before patching. CVE-2026-87719 (CVSS 9.9, Enterprise Edition only) lets a logged-in Duo Chat user hide a command in a request that triggers Advanced Search settings and password disclosure. WatchTowr Labs reported it is already watching probes that can trigger the path traversal flaw in a single HTTP request, though CISA had not added either issue to the KEV list as of Friday afternoon.

CyberScoopupdated · 22h agofirst · 4d agoVulnerability in the wild 17 sourcesCVE-2026-85706CVE-2026-87719

Related CVEs

  • 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-877199.9—
    Authenticated GraphQL Subscription Flaw Leaks Search Credentials in GitLab EE
    GitLab EE contains a critical (CVSS 9.9) deserialization flaw (CWE-502) in which an authenticated user with Duo Chat access can pass a specially crafted GraphQL subscription argument that bypasses serialization and performs a server object lookup. Via this bypass, the attacker can obtain Advanced Search instance configurations and the sensitive credentials they contain. Because the attack requires only a low-privileged account with Duo Chat access over the network, with no user interaction, any EE deployment where Duo Chat is enabled is potentially exposed, including both self-managed instances and GitLab.com. Affected versions are EE 18.3 and later before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2. No public proof-of-concept or CISA KEV listing exists for this CVE as of now, though related GitLab flaws disclosed in the same cycle are reportedly drawing internet-wide probing.
    · GitLab EE all versions from 18.3 before 19.1.8; 19.2 before 19.2.6; 19.3 before 19.3.2large

Appears with

organization CISA 1organization GitLab 1organization WatchTowr Labs 1product Duo Chat 1product GitLab CE 1product GitLab EE 1vendor CISA 1vendor GitLab 1vendor WatchTowr Labs 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.