GitLab CVSS 10 File-Read Flaw Draws In-the-Wild Probes After Disclosure
GitLab disclosed a critical vulnerability rated CVSS 9.9 in its self-hosted AI Gateway on October 2, following active malicious probing against a separate file-read flaw tracked as CVE-2026-85706. The AI Gateway vulnerability, designated CVE-2026-90970, involves a Jinja2 template injection that allows authenticated Duo users to escape a prompt sandbox and execute commands on self-hosted gateways. Meanwhile, the unauthenticated path traversal vulnerability in the repository commits API continues to attract in-the-wild exploitation across self-managed Community and Enterprise editions, exposing database credentials, SSH keys, deploy tokens, continuous integration variables, and instance secrets.
Listen to Live Briefing
Real-time synthesized voice briefing Β· Live Feeds Desk
- β GitLab disclosed a critical vulnerability in its self-hosted AI Gateway on October 2, assigning it a CVSS score of 9.9 out of 10.
- β Tracked as CVE-2026-90970, the AI Gateway flaw allows authenticated Duo users to escape a prompt sandbox and execute commands on self-hosted gateways.
- β The vulnerability involves a Jinja2 template injection in an AI-specific infrastructure component.
- β Managed services are already patched for the AI Gateway flaw, while self-hosted GitLab instances are exposed.
What changed
GitLab released a patch for a critical CVSS 9.9 prompt template sandbox escape in its self-hosted AI Gateway.
Live updates
-
GitLab Patches CVSS 9.9 AI Gateway Flaw as File-Read Probes Mount
GitLab disclosed a critical vulnerability rated CVSS 9.9 in its self-hosted AI Gateway on October 2, following active malicious probing against a separate file-read flaw tracked as CVE-2026-85706. The AI Gateway vulnerability, designated CVE-2026-90970, involves a Jinja2 template injection that allows authenticated Duo users to escape a prompt sandbox and execute commands on self-hosted gateways. Meanwhile, the unauthenticated path traversal vulnerability in the repository commits API continues to attract in-the-wild exploitation across self-managed Community and Enterprise editions, exposing database credentials, SSH keys, deploy tokens, continuous integration variables, and instance secrets.
Why it matters
DevSecOps platforms aggregate highly sensitive data, transforming basic confidentiality flaws into credential incidents that compromise entire software delivery chains. Managed services received patches for the AI Gateway remote code execution vulnerability, but self-hosted deployments remain exposed until administrators apply updates. These concurrent critical flaws increase pressure on security teams managing enterprise infrastructure.
What is confirmed
- GitLab disclosed a critical vulnerability in its self-hosted AI Gateway on October 2, assigning it a CVSS score of 9.9 out of 10.
- Tracked as CVE-2026-90970, the AI Gateway flaw allows authenticated Duo users to escape a prompt sandbox and execute commands on self-hosted gateways.
- The vulnerability involves a Jinja2 template injection in an AI-specific infrastructure component.
- Managed services are already patched for the AI Gateway flaw, while self-hosted GitLab instances are exposed.
Still unconfirmed
- Attackers can potentially harvest database credentials, SSH keys, deploy tokens, continuous integration variables, and instance secrets via CVE-2026-85706.
What to watch next
- Deployment of automated scanning modules for CVE-2026-85706
- Adoption rates of patches for the AI Gateway vulnerability CVE-2026-90970 on self-hosted servers
confidence 95%Sources used for this update (6)
- aiweekly.co β GitLab Patches CVSS 9.9 Sandbox Escape in Self-Hosted AI Gateway
- forkast.news β GitLab Patches Critical AI Gateway RCE Vulnerability β Prompt Template Sandbox Escape Rated CVSS 9.9
- securityaffairs.com β CVE-2026-90970: Critical GitLab AI Gateway Flaw Fixed
- dev.to β GitLab CVE-2026-85706: When a Path Traversal Lands in the ...
- github.com β [Module-request] CVE-2026-85706 (GitLab Path Traversal ...
- www.infoq.com β GitLab Vulnerability Under Active Exploitation Enables Unauthenticated Data Exfiltration
-
GitLab Path Traversal Flaw Triggers Credential Incidents
Malicious actors actively target a critical path traversal vulnerability in GitLab installations, exposing self-managed servers to credential theft. Tracked as CVE-2026-85706, the unauthenticated arbitrary file read vulnerability affects the repository commits API in both Community and Enterprise editions. Because DevSecOps platforms centralize sensitive data, security analysts emphasize that an unauthorized file read functions directly as a credential incident rather than a standard confidentiality breach. Attackers can potentially harvest database credentials, SSH keys, deploy tokens, continuous integration variables, and instance secrets. Security agencies and researchers confirm active probing against internet-facing servers.
Why it matters
Source-code management infrastructure faces intensifying security pressures as threat actors exploit exposed APIs to compromise enterprise environments. The vulnerability allows unauthorized external parties to bypass authentication checks and extract sensitive files from self-managed servers. Mitigation requires administrators to immediately apply official security updates released by GitLab.
What is confirmed
- CVE-2026-85706 is an unauthenticated arbitrary file read vulnerability located in the repository commits API of GitLab.
- The vulnerability impacts both GitLab Community Edition and GitLab Enterprise Edition.
- Self-managed GitLab servers frequently store database credentials, SSH keys, deploy tokens, CI/CD variables, and instance secrets.
What to watch next
- Additional telemetry regarding successful credential extraction attempts from targeted GitLab instances.
- Updates from the Cybersecurity and Infrastructure Security Agency regarding the inclusion of CVE-2026-85706 in mandatory remediation lists.
- Reports of patch adoption rates across self-managed GitLab deployments.
confidence 95%Sources used for this update (2)
-
GitLab Critical File-Read Flaw Faces Active In-the-Wild Probes
Internet-facing GitLab servers face active malicious probing days after the disclosure of a critical path traversal vulnerability. WatchTowr identified actors scanning for the flaw as the Cybersecurity and Infrastructure Security Agency confirmed active in-the-wild exploitation. The vulnerability affects both GitLab Community Edition and Enterprise Edition through the repository commits endpoint. Developers urge the prompt installation of released security updates to mitigate the risk. This unauthenticated flaw compounds existing security pressures on source-code management infrastructure.
Why it matters
CVE-2026-85706 targets the POST API repository commits endpoint of GitLab due to the body-upload helper improperly handling parameters. This unauthenticated flaw carries a maximum CVSS score, making it an immediate priority for malicious actors and defenders alike. Security teams must manage simultaneous vulnerabilities across development platforms and underlying operating systems.
What is confirmed
- CVE-2026-85706 is a critical unauthenticated path traversal vulnerability affecting GitLab Community Edition and Enterprise Edition.
- The vulnerability impacts the repository commits endpoint specifically through the body-upload helper processing the file.path parameter.
- CISA confirms active exploitation of the GitLab bug as watchTowr spots miscreants probing internet-facing servers.
What to watch next
- Reports of successful breaches stemming from CVE-2026-85706 probes
- Additional emergency updates or patches from GitLab developers
confidence 100%Sources used for this update (6)
- www.truesec.com β CVE-2026-85706: Critical GitLab Unauthenticated Arbitrary ...
- www.offsec.com β CVE-2026-85706: GitLab Unauthenticated Arbitrary File Read ...
- uk.headtopics.com β Perfect-10 GitLab bug under attack days after patch lands
- advisories.gitlab.com β GitLab Advisory Database (GLAD)
- www.techtimes.com β Latest CVEs & Actively Exploited Vulnerabilities | Tech Times
- www.heise.de β Security vulnerabilities: GitLab servers attackable with ...
-
GitLab Emergency Updates Patch Critical CI/CD Code Execution Flaws
GitLab issued emergency updates addressing two critical vulnerabilities allowing authenticated users to execute arbitrary code via crafted CI/CD regular expressions. These additions follow ongoing active threats against GitLab instances, including unauthenticated attackers exploiting the CVE-2026-85706 file-read flaw through the commits-API, which remains listed in the CISA Known Exploited Vulnerabilities catalog. Meanwhile, CISA added three Linux kernel flaws to its KEV catalog based on active exploitation evidence, prompting Red Hat to urge high-priority patching due to known public exploit code. Administrators face compounding pressures from simultaneous exploitation vectors across source-code management infrastructure and underlying operating systems.
Why it matters
The convergence of critical application-layer vulnerabilities and operating system flaws increases the attack surface for enterprise networks. GitLab instances face multiple vectors, from unauthenticated arbitrary file reads to authenticated code execution through regular expressions. Concurrently, core infrastructure faces heightened risk as CISA flags actively exploited Linux kernel vulnerabilities.
What is confirmed
- GitLab released emergency updates for two critical flaws enabling authenticated users to execute arbitrary code via crafted CI/CD regular expressions.
Still unconfirmed
- There are currently no details on how the three Linux kernel vulnerabilities added to the CISA KEV catalog are being exploited in the wild, or if they are part of a single attack chain.
What to watch next
- Confirmation of whether the new GitLab CI/CD vulnerabilities are currently being exploited in the wild.
- Additional advisories from Red Hat or CISA regarding the specific attack mechanisms of the newly flagged Linux kernel flaws.
confidence 100%Sources used for this update (3)
- thehackernews.com β CISA Flags Three Linux Kernel Vulnerabilities Exploited in the Wild
- thehackernews.com β Gitlab | Breaking Cybersecurity News | The Hacker News
- cybersecuritynews.com β Critical GitLab Bugs Let Attackers Execute Code Through Malicious CI/CD Regex
-
GitLab File-Read Flaw Persists Amid New Critical Vulnerabilities
Unauthenticated attackers continue to exploit CVE-2026-85706 to read arbitrary files in GitLab via the commits-API. This CVSS 10.0 flaw remains active in the CISA Known Exploited Vulnerabilities catalog. While GitLab users face ongoing attacks, other vendors have addressed high-severity bugs. Microsoft patched a privilege escalation flaw in Azure AI Foundry, and Check Point fixed a root code execution bug in its management servers. Additionally, public exploit code now exists for four Linux kernel vulnerabilities that allow local root access.
Why it matters
The prevalence of CVSS 10.0 flaws across diverse platforms indicates a high-risk environment for enterprise infrastructure. These vulnerabilities often allow attackers to bypass authentication or gain the highest level of system permissions. Immediate patching is required to prevent unauthorized data access and system takeovers.
What is confirmed
- CVE-2026-85706 allows unauthenticated attackers to read arbitrary files via a single HTTP request to the commits-API.
- CISA listed CVE-2026-85706 in its Known Exploited Vulnerabilities catalog.
- Microsoft released fixes for CVE-2026-85889, a CVSS 10.0 privilege escalation flaw in Azure AI Foundry.
- Check Point fixed CVE-2026-91843 to prevent root code execution on Security Management and Log Servers.
- Researcher Asim Manizada published exploit code on September 18 for four Linux kernel flaws: DirtyAH6, TUNderflow, PPPoEject, and DiagSpill.
What to watch next
- Reports of active exploitation of the newly public Linux kernel exploits
- Updates on GitLab patching rates following CISA listing
confidence 100%Sources used for this update (3)
- thehackernews.com β Microsoft Patches CVSS 10.0 Azure AI Foundry Flaw Enabling Unauthorized Privilege Escalation
- thehackernews.com β Public Exploits Released for Four Linux Kernel Flaws That Enable Local Root
- securityaffairs.com β Check Point Fixes Critical CVE-2026-91843 Allowing Root Code Execution
-
GitLab Path Traversal Flaw CVE-2026-85706 Remains Under Active Exploitation
Unauthenticated attackers continue to exploit CVE-2026-85706 to read arbitrary files via a single HTTP request to the commits-API. The vulnerability has a maximum CVSS score of 10.0 and provides unauthorized access to sensitive files within software development environments. CISA has officially listed the flaw in its Known Exploited Vulnerabilities catalog. Security entities report ongoing attacks and urge immediate patching to protect affected systems.
Why it matters
Path traversal vulnerabilities in development tools can expose private keys, configuration files, and proprietary source code. This specific flaw allows external actors to bypass authentication to access internal system files.
What is confirmed
- CVE-2026-85706 allows unauthenticated attackers to read arbitrary files through a single HTTP request to the commits-API.
- The vulnerability carries a maximum CVSS score of 10.0.
- CISA added the path traversal flaw to its Known Exploited Vulnerabilities catalog.
What to watch next
- Release of specific exploit payloads used in the wild
- Updates from GitLab on the number of compromised instances
- CISA guidance on remediation verification
confidence 100%Sources used for this update (2)
- securityaffairs.com β U.S. CISA adds Acronis Backup, Cisco ISE, and Google Pixel flaws to its Known Exploited Vulnerabilities catalog
- cyberpress.org β Jenkins Fixes 20 Plugin Vulnerabilities Enabling RCE, Sandbox Bypass and Credential Theft
-
CISA Tracks Active Exploitation of GitLab CVSS 10 File-Read Flaw
Unauthenticated attackers are using CVE-2026-85706 to read arbitrary files through a single HTTP request to the commits-API. The vulnerability carries a maximum CVSS score of 10.0 and allows unauthorized access to sensitive files in software development environments. CISA has added the path traversal flaw to its Known Exploited Vulnerabilities catalog. Security entities report that these attacks are currently ongoing and advise immediate patching to secure affected systems.
Why it matters
Path traversal vulnerabilities allow attackers to access files outside of the intended folder. In development environments, this can expose secrets, source code, or configuration files.
What is confirmed
- CVE-2026-85706 allows unauthenticated attackers to read arbitrary files via a single HTTP request to the commits-API.
- The vulnerability has a CVSS score of 10.0.
- CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog.
What to watch next
- Confirmation of successful patch deployment across major enterprise environments
- Reports of specific data exfiltrated during the ongoing attacks
confidence 100%Sources used for this update (2)
- cybersecuritynews.com β Check Point Vulnerability Lets Remote Hackers Gain Root Access Without Authentication
- forkast.news β Two Unauthenticated Lockpicks for the Enterprise Vault: Delinea Secret Serverβs Double Critical Disclosure
-
CISA Adds Critical GitLab File-Read Flaw to Known Exploited Vulnerabilities List
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog. This maximum-severity path traversal flaw carries a CVSS score of 10.0 and allows unauthenticated attackers to read arbitrary files via a single HTTP request to the commits-API. Malicious actors are actively exploiting the vulnerability to access sensitive files within software development environments. CISA and other security entities warn that these attacks are ongoing, urging immediate patching to prevent unauthorized data access.
Why it matters
The vulnerability targets the commits-API, making it accessible to anyone with network access to the instance. Because GitLab environments often house proprietary source code and secrets, this flaw poses a high risk of intellectual property theft.
What is confirmed
- The GitLab vulnerability has a CVSS score of 10.0.
- CISA has added the GitLab flaw to its Known Exploited Vulnerabilities catalog.
- Threat actors are actively exploiting this vulnerability.
- The flaw allows unauthenticated users to access sensitive files from software-development environments.
What to watch next
- Reports of specific data breaches resulting from the exploit
- GitLab updates on the number of affected installations
- Identification of specific threat actor groups targeting the flaw
confidence 100%Sources used for this update (4)
- www.yahoo.com β Malicious actors already using critical GitLab flaw, CISA and others warn
- www.infosecurity-magazine.com β Hackers Exploit Maximum Severity Flaw in GitLab
- securityaffairs.com β U.S. CISA adds GitLab, JFrog Artifactory, and ConnectWise ScreenConnect flaws to its Known Exploited Vulnerabilities catalog
- www.bleepingcomputer.com β CISA: Critical VMware RCE flaw now exploited by ransomware gangs
-
GitLab CVSS 10 Flaw Triggers In-the-Wild Probes
GitLab urges users to patch a maximum-severity path traversal vulnerability carrying a CVSS score of 10.0, identified as CVE-2026-85706. The flaw allows unauthenticated attackers to read arbitrary files using a single HTTP request via the commits-API. Within hours of disclosure, security researchers and threat actors initiated internet-wide probing and active exploitation of the vulnerability. The U.S. Cybersecurity and Infrastructure Security Agency warned that hackers are now exploiting the max severity GitLab flaw in attacks.
Why it matters
GitLab issued emergency security updates to address the unauthenticated file-read vulnerability affecting its platform. The rapid transition from disclosure to active exploitation highlights the speed at which threat actors weaponize critical API flaws. Organizations utilizing GitLab are instructed to apply patches immediately to prevent system compromise.
What is confirmed
- GitLab patched a maximum-severity path traversal vulnerability assigned CVE-2026-85706 with a CVSS score of 10.0.
- The vulnerability allows unauthenticated full file read via a single HTTP request through the commits-API.
- The U.S. Cybersecurity and Infrastructure Security Agency warned that hackers are now exploiting the max severity GitLab flaw in attacks.
What to watch next
- Additional CISA advisories or emergency directives regarding CVE-2026-85706
- Reports of specific enterprise compromises stemming from the commits-API flaw
- Release of automated patch adoption statistics from the GitLab ecosystem
confidence 100%Sources used for this update (10)
- The Hacker News β GitLab CVSS 10 File-Read Flaw Draws In-the-Wild Probes After Disclosure
- BleepingComputer β GitLab urges users to patch max severity path traversal flaw
- watchTowr β Rapid Reaction: GitLab Path Traversal Vulnerability (CVE-2026-85706)
- forkast.news β One HTTP Request, Every File on the Server: GitLabβs CVSS 10 Commits-API Flaw Hits Active Exploitation Within Hours
- CyberScoop β GitLabβs critical flaw is already drawing internet-wide probes
- Field Effect β GitLab fixes critical vulnerability as internet-wide probing begins
- linkedin.com β GitLab Issues Emergency Security Update For Maximum-Severity Vulnerability
- www.bleepingcomputer.com β CISA: Hackers now exploit max severity GitLab flaw in attacks
- cybersecuritynews.com β Critical Dell ObjectScale Vulnerabilities Allows Malicious Users to Compromise the Affected system
- securityaffairs.com β GitLab CVE-2026-85706: One HTTP Request, No Authentication, Full File Read β Exploited Within 24 Hours
Community Sentiment: How do you assess this situation?
Voice your perspective Β· Real-time aggregated sentiment from the Live Feeds community