Tag Archives: RubyOnRails

About Remote Code Execution - GitLab (CVE-2026-110264) vulnerability

About Remote Code Execution - GitLab (CVE-2026-110264) vulnerability

About Remote Code Execution - GitLab (CVE-2026-110264) vulnerability. GitLab is a platform for hosting code, collaborative software development, project management, and automating application testing and releases. GitLab CE is the free, open-source version of the platform, while GitLab EE is the enterprise version with additional features. Under certain conditions, the vulnerability in GitLab CE/EE allows an unauthenticated attacker to execute arbitrary code on the server. The vulnerability existed in GitLab for approximately 12 years and affected GitLab CE/EE versions 7.0 and later.

The vulnerability is caused by the following issue. GitLab uses the Ruby programming language to implement a significant part of its server-side logic. In particular, the platform's backend is built on Ruby on Rails, a web framework written in Ruby. Ruby also uses additional libraries and built-in components to perform various tasks. One of these is Onigmo, a regular expression engine responsible for searching and processing text based on predefined patterns. According to Censys research, the vulnerability is related to the processing of Org mode files with the .org extension. When converting these files to HTML, GitLab uses the org-ruby library, which processes user-defined keywords in documents, such as #+TODO:. An attacker can provide a specially crafted value for such a keyword, triggering an overflow in the Onigmo regular expression engine, resulting in memory corruption. Under certain conditions, this can lead to arbitrary code execution on the GitLab server. To exploit the vulnerability, an attacker needs to upload a specially crafted file to a public project. For example, if self-registration is enabled and users are allowed to create public projects, an attacker can register an account and create their own project. Once the file is uploaded, the vulnerable handler can be triggered simply by opening the file's preview page without authentication.

A compromised GitLab server may give an attacker access to project source code, access tokens, credentials, and other sensitive information. After gaining control of the server, an attacker may modify source code or build processes to inject malicious code into distributed applications. In addition, a compromised GitLab server can serve as a starting point for further attacks against the organization's internal infrastructure.

⚙️ The vulnerability has been fixed in versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, and 18.11.13. Infrastructure managed by GitLab itself, including GitLab.com and GitLab Dedicated, is already protected against this vulnerability. If GitLab was installed from unofficial packages and uses a custom Ruby version, updating GitLab alone is not sufficient. This applies, for example, to custom-built GitLab versions and installations using custom container images. In such cases, Ruby must also be updated separately to version 3.3.13, 3.4.12, or 4.0.9 or later. This is because the fix for CVE-2026-110264 was implemented directly in Ruby, not in the GitLab code. The fix is already included in the official GitLab Linux packages and container images.

The GitLab security team has released two detection rules to identify potential attacks against self-hosted GitLab instances: Onigmo native worker crash and Org mode render error burst.

🛠 PoC exploits have been available on GitHub since October 22.

👾 There is currently no evidence that the vulnerability has been exploited in the wild.

🌐 According to Shadowserver, more than 10,000 vulnerable GitLab instances are exposed to the Internet.

August Linux Patch Wednesday

August Linux Patch Wednesday

August Linux Patch Wednesday. A total of 3,060 vulnerabilities. For comparison, there were 2,017 in July. That's a 52% increase and another new record. This time, there are 1,354 vulnerabilities in the Linux Kernel and 447 in Chromium. For 3 vulnerabilities, there are signs of exploitation in the wild:

🔻 RCE - Jenkins (CVE-2026-53435). Jenkins is a development automation server used to build, test, and deploy software. The vulnerability allows a remote authenticated attacker to use the Script Console to execute arbitrary code and read files from the Jenkins controller. The vulnerability was added to the VulnCheck KEV on June 15 and fixed in RedOS on August 12.

🔻 CodeInj - WordPress (CVE-2026-60137). WordPress is a popular open-source CMS for creating websites and blogs. The vulnerability leads to a blind SQL injection in the WordPress core, allowing a remote unauthenticated attacker to read user accounts and password hashes from the WordPress database. Code execution is then possible by installing a malicious plugin. Multiple public exploits are available. The vulnerability was added to the CISA KEV catalog on July 21. A fix for the wordpress package in the Debian repository was released on July 23.

🔻 RCE - SPIP (CVE-2026-77647). SPIP is an open-source CMS for creating and collaboratively editing websites. The vulnerability allows an unauthenticated remote attacker to execute arbitrary PHP code. The vulnerability was added to the VulnCheck KEV on August 20. A fix for the spip package in the Debian repository was released on August 18.

Strictly speaking, the report contains one more vulnerability RCE - WinRAR (CVE-2025-8088) that is being exploited in the wild. The vulnerability was fixed in the clamav package in the Alt Linux repository. However, exploitation is only possible on Windows, so it is out of scope.

Another 127 vulnerabilities are not known to be exploited in the wild, but public exploits are available for them, or there are indications that such exploits exist. Notable examples include:

🔸 RCE - Action Pack "KindaRails2Shell" (CVE-2026-66066). Action Pack is a component of Ruby on Rails responsible for handling web requests, routing, and generating responses. An attacker can upload a specially crafted image to a vulnerable application and achieve remote code execution.

🔸 RCE - WordPress "XSS2Shell" (CVE-2026-64638). The attack chain allows an unauthenticated XSS on the login page to be escalated to arbitrary PHP code execution.

🔸 CodeInj - PHP (CVE-2026-17543). Improper escaping of backslashes in attacker-controlled parameters can lead to a trivial SQL injection in PHP.

🔸 EoP - Linux Kernel "Zapscape" (CVE-2026-64561). This KVM escape vulnerability allows an attacker to break out of a virtual machine in KVM/x86 environments and execute commands on the host with root privileges.

🔸 EoP - Linux Kernel "OVSwrap" (CVE-2026-64531), Linux Kernel "SCTPhantom" (CVE-2026-64564), Linux Kernel "Ubuntu PPPoL2TP" (CVE-2026-68398). These vulnerabilities allow a local attacker to escalate privileges to root.

🔸 AuthBypass - Traefik (CVE-2026-48020). Traefik is an HTTP reverse proxy and load balancer. A high-severity vulnerability in the StripPrefix middleware allows an unauthenticated attacker to bypass route-level authentication and authorization.

🗒 Full Vulristics report