ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “GitLab CE”

4 items in the last 3d

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllExploit / PoC 4
SeverityAllcritical 3high 1medium 0low 0info 0

A maximum severity GitLab flaw could turn your CI/CD server into an attacker’s treasure trove

GitLab patched maximum-severity CVE-2026-85706, an unauthenticated path traversal enabling arbitrary file reads; CISA added it to KEV amid observed in-the-wild probes.

CVE-2026-85706 is a CVSS 10.0 path traversal in GitLab's repository commits API caused by improper confinement and missing authentication enforcement, allowing arbitrary file reads in a single unauthenticated HTTP request. It affects GitLab CE and EE versions 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, and was reported via GitLab's HackerOne bug bounty. CISA added the flaw to its Known Exploited Vulnerabilities catalog, and watchTowr Intel reports already observing in-the-wild probes; GitLab is used by roughly 50% of the Fortune 100 with over 50 million registered users. Defenders are advised to patch immediately, rotate any exposed secrets, and hunt logs for HTTP POST requests to /api/v4/projects/{id}/repository/commits/ URIs containing file.path parameters.

CSO Online · 2d agoExploit / PoC in the wild 18 sourcesCVE-2026-85706

CVE-2026-85706: Critical GitLab Path Traversal Exploited in the Wild

CVE-2026-85706, a CVSS 10.0 unauthenticated path traversal in GitLab CE/EE, is actively exploited and was added to CISA's KEV catalog.

GitLab patched CVE-2026-85706, a critical path traversal (CWE-22) in the repository commits API scoring CVSSv3.1 10.0, allowing unauthenticated arbitrary file reads on affected self-managed servers under certain conditions. CISA added it to the KEV catalog on September 11, 2026, citing active exploitation, with a September 14 remediation deadline and BOD 26-04 forensic triage requirements. Fixed versions are 19.1.8, 19.2.6, and 19.3.2; the release also fixes 17 other vulnerabilities including CVE-2026-87719, a CVSS 9.9 insecure deserialization flaw in GitLab EE.

Rapid7 Blogupdated · 2d agofirst · 2d agoExploit / PoC in the wild 18 sourcesCVE-2026-85706CVE-2026-877192

GitLab CVE-2026-85706 Added to CISA KEV

CISA added CVE-2026-85706 to KEV: a path traversal in GitLab CE/EE letting unauthenticated attackers read arbitrary files.

CVE-2026-85706 is a severe path traversal flaw in GitLab CE and EE that permits unauthenticated remote actors to retrieve arbitrary files from affected self-managed deployments. CISA has added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog, indicating exploitation has been observed. Organizations running self-managed GitLab instances should prioritize patching.

SOCRadarupdated · 2d agofirst · 2d agoExploit / PoC in the wild 18 sourcesCVE-2026-85706

CISA: Hackers now exploit max severity GitLab flaw in attacks

CISA added max-severity GitLab CVE-2026-85706 to its exploited-flaws catalog after watchTowr observed probing of unpatched servers.

CISA added CVE-2026-85706, a maximum-severity GitLab flaw caused by missing authentication enforcement and improper path confinement in the repository commits API, to its actively exploited vulnerabilities catalog. Unauthenticated attackers can read credentials, secrets, and arbitrary files from vulnerable servers via a single HTTP request. GitLab patched the issue in CE/EE versions 19.3.2, 19.2.6, and 19.1, and federal agencies have three days to remediate under BOD 26-04. watchTowr reported in-the-wild probes for unpatched GitLab servers, and this is the fourth GitLab vulnerability CISA has tagged as actively exploited since November 2021.

BleepingComputerupdated · 2d agofirst · 2d agoExploit / PoC in the wild 18 sourcesCVE-2026-85706CVE-2021-22175CVE-2021-39935