---
title: GitLab Org-mode file render burst from a single client
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > GitLab Org-mode file render burst from
  a single client
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# GitLab Org-mode file render burst from a single client

{% alert level="danger" %}
This rule is part of a beta feature. To learn more, [contact Support](https://docs.datadoghq.com/help/).
{% /alert %}
Classification:attackTactic:[TA0001-initial-access](https://attack.mitre.org/tactics/TA0001)Technique:[T1190-exploit-public-facing-application](https://attack.mitre.org/techniques/T1190) 
## Goal{% #goal %}

Detects a burst of Org-mode (`.org`) file renders from a single GitLab client. Five or more `.org` file views within 30 minutes from one client signal repeated attempts to deliver a CVE-2026-110264 payload.

## Strategy{% #strategy %}

This rule monitors GitLab request logs for `Projects::BlobController#show` requests where `@http.url_details.path` ends in `.org`. These requests render Org-mode content through the `org-ruby` library, which passes document keywords into the Onigmo regular expression engine. CVE-2026-110264 is an unauthenticated remote code execution vulnerability in which a crafted `#+TODO:` line overflows an Onigmo repeat counter and causes an out-of-bounds write. Landing a working payload usually takes several attempts, and each attempt produces a blob render request whether it ends in a timeout, a worker crash, or a quiet failure. Viewing `.org` files is rare in most GitLab environments, so a concentrated burst from one client is unusual. The rule serves as a request-log proxy for the GitLab Security Incident Response Team (SIRT) render error burst detection, which relies on the GitLab exceptions log.

## Triage & Response{% #triage--response %}

- Review the `.org` paths requested by `{{@meta.client_id}}` and identify the projects in `{{@meta.project}}`, noting whether the client controls the files or they belong to other users.
- Check whether `{{@meta.client_id}}` maps to an authenticated user (`{{@meta.user}}`) or an anonymous client. Review `{{@meta.remote_ip}}` for scanner, proxy, or hosting provider ranges.
- Determine whether the client recently created or pushed the `.org` files, since a legitimate documentation workflow can produce repeated renders of the same notes.
- Inspect response status codes and request durations for the burst, and look for `5xx` responses, Workhorse `502` errors, or Puma worker restarts on the GitLab web service hosts at the same time.
- Examine recent commits, merge requests, wiki pages, and snippets containing `.org` content from the client for unusually long or heavily repetitive `#+TODO:` lines.
- Verify that the GitLab instance runs a version with the CVE-2026-110264 fix. Review the web service host for unexpected child processes or outbound connections.
