CVE-2026-2441 CrowdStrike LogScale · LogScale

Detect CVE-2026-2441: Google Chromium CSS Use-After-Free Exploitation in CrowdStrike LogScale

Detects exploitation of CVE-2026-2441, a use-after-free vulnerability in the CSS engine of Google Chromium. This vulnerability is actively exploited in the wild (CISA KEV) and can allow remote code execution via a malicious web page. Detection focuses on abnormal Chromium renderer process behavior, suspicious child process spawning, and memory corruption indicators consistent with UAF exploitation.

MITRE ATT&CK

Tactic
Initial Access Execution Defense Evasion

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName=ProcessRollup2
| ParentBaseFileName IN ("chrome.exe", "chromium.exe", "chromium")
| CommandLine = "*--type=renderer*"
| FileName IN ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "certutil.exe", "bitsadmin.exe", "schtasks.exe")
| groupBy([aid, ComputerName, UserName, ParentBaseFileName, FileName, CommandLine])
| rename ComputerName as host, UserName as user, ParentBaseFileName as parent_process, FileName as child_process, CommandLine as child_cmdline
| sort timestamp desc
critical severity high confidence

CrowdStrike Falcon LogScale (CQL) query identifying Chrome renderer processes spawning suspicious system binaries, indicative of CVE-2026-2441 exploitation.

Data Sources

CrowdStrike Falcon Endpoint ProtectionCrowdStrike LogScale

Required Tables

ProcessRollup2

False Positives & Tuning

  • CrowdStrike sensor itself or other AV products interacting with Chrome process tree
  • Legitimate Chrome extension native messaging hosts that launch system processes
  • Developer or QA environments running automated Chrome testing with scripted subprocess invocations

Other platforms for CVE-2026-2441


Testing Methodology

Validate this detection against 4 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 Chromium Renderer Spawning cmd.exe

    Expected signal: Sysmon Event ID 1 showing chrome.exe (with --type=renderer in command line) as ParentImage for cmd.exe process creation. DeviceProcessEvents in MDE will show the renderer→cmd.exe lineage.

  2. Test 2Chromium Renderer Spawning PowerShell with Network Callback

    Expected signal: Sysmon Event ID 1 (process create: powershell under chrome renderer), Sysmon Event ID 3 (network connection from powershell to 127.0.0.1:8080). Elastic EQL sequence rule should correlate both events.

  3. Test 3Validate Unpatched Chrome Version Detection via Asset Inventory

    Expected signal: Registry query results showing Chrome version strings per host. CrowdStrike RTR or MDE LiveResponse will log the query execution.

  4. Test 4CSS Object Lifecycle Stress Test for UAF Trigger Research

    Expected signal: On a vulnerable build: renderer process crashes (SIGSEGV or similar) visible in /var/log/syslog or Chromium crash reports under ~/.config/chromium/Crash Reports/. On a patched build: no crash, normal page operation.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections