---
title: GitLab Org-mode renderer forced via preview file_path on a non-Org file
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > GitLab Org-mode renderer forced via
  preview file_path on a non-Org file
---

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

# GitLab Org-mode renderer forced via preview file_path on a non-Org file

{% 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 GitLab blob preview requests that force the Org-mode renderer onto content that is not an Org file. A preview whose `file_path` ends in `.org` on a non-Org URL signals an attempt to reach the CVE-2026-110264 code path without committing a file.

## Strategy{% #strategy %}

This rule monitors GitLab request logs for `Projects::BlobController#preview` requests (`@meta.caller_id`) where a `file_path` entry in `@params` ends in `.org` while the requested path in `@http.url_details.path` does not reference an Org file. GitLab selects the markup renderer from the `file_path` basename, so supplying a `.org` name sends arbitrary preview content through the `org-ruby` library and into the Onigmo regular expression engine. CVE-2026-110264 is a remote code execution vulnerability in which a crafted `#+TODO:` line overflows an Onigmo repeat counter and causes an out-of-bounds write. Delivering the payload through the preview endpoint avoids leaving a committed `.org` file in the repository, which makes this a quieter exploitation path than rendering a stored file. Legitimate previews of Org files reference the `.org` file in the request path, so this mismatch has no common benign cause.

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

- Examine the `@params` array on the request from `{{@meta.client_id}}` to confirm that `file_path` ends in `.org` while `{{@http.url_details.path}}` points to a different file or resource.
- Identify the user or token behind `{{@meta.client_id}}` and the project in the request. Determine whether the account is expected to edit or preview files in that project.
- Determine whether the request was a legitimate preview of a new `.org` file by checking whether the URL ends at a ref or directory and whether the project contains Org documentation.
- Review other activity from `{{@meta.client_id}}` around the same time, such as repeated preview requests, `Projects::BlobController#show` requests for `.org` files, or Workhorse `502` responses.
- Check the source IP and user agent against known scanners, security testing tools, or researchers working on the Org-mode vulnerability.
- Verify that the GitLab instance runs a version with the CVE-2026-110264 fix. Review the GitLab web service host for rendering errors, worker crashes, or unexpected child processes around the time of the request.
