---
title: GitLab Workhorse 502 on Org-mode file render
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > GitLab Workhorse 502 on Org-mode file
  render
---

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

# GitLab Workhorse 502 on Org-mode file render

{% 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 HTTP 502 responses from GitLab Workhorse on Org-mode (`.org`) file view requests. A burst of failed `.org` renders from one client signals attempted exploitation of CVE-2026-110264.

## Strategy{% #strategy %}

This rule monitors GitLab Workhorse access logs for responses where `@http.status_code` is `502` and `@uri` targets an Org-mode file on the `/-/blob/` file view route. GitLab renders `.org` files 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. When a malicious `.org` file crashes the Puma worker during rendering, Workhorse has no upstream response to relay and returns a `502`. The crashed worker never writes its own request log entry, so the Workhorse access log line is often the only record of the attempt. A single `502` raises a Medium severity signal, and three or more within 30 minutes raise a High severity signal. Successful exploitation that does not crash the worker produces a normal response, so this rule surfaces failed or unreliable exploit attempts rather than every compromise.

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

- Determine whether `{{@network.client.ip}}` is the real client or a load balancer or reverse proxy address. If it is a proxy, identify the originating client from proxy or Rails request logs by matching timestamps and paths.
- Identify the requested `.org` file and project from `{{@uri}}`. Check whether the file was recently added or changed by the same client or a newly created account.
- Check the GitLab web service hosts for Puma worker crashes, segmentation faults, or container restarts at the time of the `502` responses.
- Review the Rails request and exception logs for `Projects::BlobController#show` requests on the same `.org` path and for render timeouts, which indicate attempts that did not crash the worker.
- Examine other activity from `{{@network.client.ip}}` across GitLab request and audit logs for enumeration, new access tokens, or access to additional projects.
- Verify that the GitLab instance runs a version with the CVE-2026-110264 fix. Review the web service host for unexpected child processes, outbound connections, or new files owned by the `git` user.
