CVE-2026-52806 CrowdStrike LogScale · LogScale

Detect CVE-2026-52806: Gogs RCE via git rebase --exec Argument Injection in PR Merge in CrowdStrike LogScale

Detects exploitation of CVE-2026-52806, a critical command injection vulnerability (CWE-77) in Gogs versions prior to 0.14.3. An attacker can inject arbitrary shell commands via the git rebase --exec argument during pull request merge operations, leading to remote code execution on the Gogs server. A public PoC is available.

MITRE ATT&CK

Tactic
Execution Persistence Lateral Movement

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName = ProcessRollup2
| where ImageFileName matches regex ".*git(\.exe)?$"
  and CommandLine matches regex "rebase.*--exec"
  OR (
    ParentBaseFileName in ("gogs", "gogs.exe")
    and ImageFileName matches regex ".*(bash|sh|curl|wget|nc|ncat|python[0-9.]*|perl|cmd\.exe|powershell\.exe)$"
  )
| eval InjectionType = case(
    CommandLine matches regex "--exec[= ]['"]?[^'"]*[;&|`$]", "ArgumentInjection",
    ParentBaseFileName in ("gogs", "gogs.exe"), "SuspiciousChildFromGogs",
    "Unknown"
  )
| table timestamp, ComputerName, UserName, ParentBaseFileName, ImageFileName, CommandLine, InjectionType
| sort timestamp desc
critical severity high confidence

CrowdStrike Falcon Logscale (CQL) query detecting git rebase --exec command injection and suspicious process spawning from Gogs parent processes using ProcessRollup2 telemetry.

Data Sources

CrowdStrike Falcon SensorCrowdStrike Falcon Process Events

Required Tables

ProcessRollup2

False Positives & Tuning

  • Developers running git rebase --exec on workstations where Gogs is installed and the CrowdStrike sensor is deployed
  • Legitimate scheduled tasks running under the Gogs service account that spawn utilities like curl for health checks
  • Authorized red team exercises testing Gogs exploitation chains in lab environments with sensor coverage

Other platforms for CVE-2026-52806


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate git rebase --exec argument injection via crafted PR branch name

    Expected signal: Process creation event: git with args [rebase, --exec, id > /tmp/cve_rce_proof.txt, target]; child process creation: sh -c 'id > /tmp/cve_rce_proof.txt'; file creation event at /tmp/cve_rce_proof.txt

  2. Test 2Gogs suspicious child process simulation — reverse shell via curl

    Expected signal: Process creation event showing bash or curl with parent process name 'gogs'; network connection attempt from gogs-named process to 127.0.0.1:9999

  3. Test 3Persistence via cron injection post-Gogs RCE simulation

    Expected signal: Process creation: git rebase --exec with crontab modification command; crontab process invocation; file write to /tmp/cve_persist_marker.txt; audit log entry for crontab modification

Unlock Pro Content

Get the full detection package for CVE-2026-52806 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections