Threat reportVulnerabilityTL-2026-2838
Multiple Vulnerabilities in Microsoft Edge prior to 154.0.4258.53 (HK GovCERT A26-10-03)
Hong Kong GovCERT reports 37 CVEs fixed in Microsoft Edge 154.0.4258.53 (Chromium-sourced), with potential impact including remote code execution, denial of service, information disclosure, security restriction bypass, spoofing and tampering. No in-the-wild exploitation is reported; users should update to 154.0.4258.53 or later.
Key facts
Detection coverage
As of 2026-10-02, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2838 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Edge Spawning Shell/Script/LOLBin Child — Sandbox Escape Indicator (SPL)
Detects msedge.exe (especially sandboxed --type=renderer, gpu-process or utility children) spawning cmd, PowerShell, WSH, mshta, rundll32, regsvr32, certutil, bitsadmin, curl, wmic and similar LOLBins. Edge does not legitimately launch these, so a hit is consistent with successful exploitation of a Chromium renderer flaw chained with a sandbox escape (several A26-10-03 CVEs are rated CVSS 9.6 with scope change, e.g. CVE-2026-85047 sandbox escape via crafted HTML) followed by post-exploitation command execution. No in-the-wild exploitation has been reported for this advisory's CVEs.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1203, T1068, T1211, T1059
- Data sources: sysmon, XmlWinEventLog:Microsoft-Windows-Sysmon/Operational (EventCode 1)
- Severity: high
- Confidence: medium
Splunk SPL
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 ParentImage="*msedge.exe"
| where match(lower(Image),".(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|certutil|bitsadmin|curl|wmic|msiexec|cmstp|installutil|msbuild|schtasks|reg|net|net1|whoami)[.]exe$")
| eval edge_proc=case(like(ParentCommandLine,"%--type=renderer%"),"renderer", like(ParentCommandLine,"%--type=gpu-process%"),"gpu-process", like(ParentCommandLine,"%--type=utility%"),"utility", like(ParentCommandLine,"%--type=%"),"other-child", true(),"browser-main")
| eval sandbox_escape_suspect=if(edge_proc!="browser-main","yes","no")
| table _time host User ParentImage ParentCommandLine edge_proc sandbox_escape_suspect Image CommandLine IntegrityLevel Hashes ProcessGuid
| sort - sandbox_escape_suspect, - _timeMicrosoft KQL
let LolBins = dynamic(['cmd.exe','powershell.exe','pwsh.exe','wscript.exe','cscript.exe','mshta.exe','rundll32.exe','regsvr32.exe','certutil.exe','bitsadmin.exe','curl.exe','wmic.exe','msiexec.exe','cmstp.exe','installutil.exe','msbuild.exe','schtasks.exe','reg.exe','net.exe','net1.exe','whoami.exe']);
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ 'msedge.exe'
| where FileName in~ (LolBins)
| extend EdgeProcessType = case(InitiatingProcessCommandLine has '--type=renderer', 'renderer', InitiatingProcessCommandLine has '--type=gpu-process', 'gpu-process', InitiatingProcessCommandLine has '--type=utility', 'utility', InitiatingProcessCommandLine has '--type=', 'other-child', 'browser-main')
| extend SandboxEscapeSuspect = EdgeProcessType != 'browser-main', EdgeVersion = InitiatingProcessVersionInfoProductVersion
| extend UnpatchedBuild = isnotempty(EdgeVersion) and parse_version(EdgeVersion) < parse_version('154.0.4258.53')
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, ProcessIntegrityLevel, EdgeProcessType, SandboxEscapeSuspect, EdgeVersion, UnpatchedBuild, InitiatingProcessCommandLine, SHA256
| order by SandboxEscapeSuspect desc, Timestamp descSigma
title: Microsoft Edge Spawning Shell, Scripting or LOLBin Child Process
id: 2a94d6e8-51c7-4b3f-8e60-9f1b7d3a5c24
status: experimental
description: Detects msedge.exe spawning command interpreters, script hosts or common living-off-the-land binaries. Edge does not legitimately launch these; a hit is consistent with exploitation of a Chromium renderer vulnerability plus sandbox escape (e.g. CVE-2026-85047, CVE-2026-87438, CVE-2026-87464 in HK GovCERT A26-10-03) followed by post-exploitation execution. No in-the-wild exploitation reported for this advisory.
references:
- https://www.govcert.gov.hk/en/alerts_detail.php?id=2092
- https://nvd.nist.gov/vuln/detail/CVE-2026-85047
- https://nvd.nist.gov/vuln/detail/CVE-2026-87464
author: Threadlinqs Team
date: 2026/10/02
tags:
- attack.execution
- attack.t1203
- attack.t1059
- attack.privilege-escalation
- attack.t1068
- attack.defense-evasion
- attack.t1211
- cve.2026-85047
- cve.2026-87438
- cve.2026-87464
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith: '\msedge.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
- '\wmic.exe'
- '\msiexec.exe'
- '\cmstp.exe'
- '\installutil.exe'
- '\msbuild.exe'
- '\schtasks.exe'
- '\whoami.exe'
condition: selection_parent and selection_child
falsepositives:
- Enterprise web apps or extensions that launch helper executables via registered protocol handlers
- Developers or admins launching tooling from browser-based consoles
level: high
Known false positives:
- Enterprise web apps or extensions launching helper executables via registered protocol handlers
- Administrators launching tooling from browser-based consoles
Tuning notes: Treat edge_proc != browser-main (renderer/gpu-process/utility parent) as high priority: sandboxed Edge processes should never spawn children. Allowlist specific CommandLine patterns for known internal protocol handlers rather than excluding whole binaries. Extend the Image list for your environment (e.g. python.exe, node.exe).
- Edge Memory-Corruption Crash on Unpatched Build — Exploitation Indicator (KQL) · unlock with TL Creds
- Edge Spawning Shell/Script/LOLBin Child — Sandbox Escape Indicator (KQL) · unlock with TL Creds
- Edge-Spawned LOLBin Making External Connection — Payload Staging/C2 (KQL) · unlock with TL Creds
- Edge Memory-Corruption Crash on Unpatched Build — Exploitation Indicator (Sigma) · unlock with TL Creds
- Edge Spawning Shell/Script/LOLBin Child — Sandbox Escape Indicator (Sigma) · unlock with TL Creds
- Edge-Spawned LOLBin Making External Connection — Payload Staging/C2 (Sigma) · unlock with TL Creds
- Edge Memory-Corruption Crash on Unpatched Build — Exploitation Indicator (SPL) · unlock with TL Creds
- Edge-Spawned LOLBin Making External Connection — Payload Staging/C2 (SPL) · unlock with TL Creds
Indicators of compromise
As of 2026-10-02, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-2838.
Technical analysis
On 2026-10-02 Hong Kong GovCERT published Security Alert A26-10-03 covering multiple vulnerabilities in Microsoft Edge prior to version 154.0.4258.53. The advisory lists 37 CVE identifiers (CVE-2026-85047, CVE-2026-87438, CVE-2026-87464, CVE-2026-87481 to -87483, -87486, -87488, -87503, -87517, -87518, -87520, -87522, -87534, -87545, -87552, -87555, -87576, -87595, -87597, -87640, -87643, CVE-2026-93372 to -93383 and CVE-2026-93385 to -93387) and states that successful exploitation could lead to remote code execution, denial of service, information disclosure, security restriction bypass, spoofing or tampering. The recommended action is to update Microsoft Edge to 154.0.4258.53 or later.
Microsoft's Edge security release notes show 154.0.4258.53 (Stable) was released 2026-10-01, after 154.0.4258.48 on 2026-09-29, and that it incorporates the latest Chromium security updates. At the time of the notes, no CVEs were yet listed for that build and no zero-day or exploited-in-the-wild flag was noted; Microsoft points to the Security Update Guide for CVE detail.
NVD records for a sample of the listed CVEs show they are Chromium/Google Chrome issues whose NVD descriptions are scoped to Chrome fixed versions 152.0.7977.82, 153.0.8010.36 and 153.0.8010.52 (several on Android or iOS). Examples: CVE-2026-85047 (improper input validation in Transactions Platform, Chrome iOS < 152.0.7977.82, CWE-20, CVSS 9.6, sandbox escape via crafted HTML page); CVE-2026-87438 (out-of-bounds write in WebGL, Chrome Android < 153.0.8010.36, CWE-787, CVSS 9.6); CVE-2026-87464 (use-after-free in WebGL, Chrome < 153.0.8010.36, CWE-416, CVSS 9.6); CVE-2026-93372 (WebGL buffer overflow, Chrome Android < 153.0.8010.52, CWE-121, CVSS 9.6); CVE-2026-87517 (race condition origin-policy bypass, iOS, CVSS 3.1); CVE-2026-87545 (information disclosure, iOS Mobile component, CWE-200, CVSS 6.5); CVE-2026-87640 (out-of-bounds read in WebView, Android, CWE-125, CVSS 6.1); CVE-2026-93380 (FileSystem race condition by a compromised renderer, CWE-367, CVSS 3.1). Only a subset of the 37 CVEs was individually checked; the rest are taken from the GovCERT list. The severity mix is wide, from Low to Critical.
None of the sampled CVEs appear in the CISA Known Exploited Vulnerabilities catalog. The KEV feed does contain two September 2026 Chromium V8 entries (CVE-2026-87491, CVE-2026-85046) that are not in this advisory's CVE list. Chrome 154 itself shipped on 2026-09-22 (154.0.8037.57/.58) with 108 security fixes, 11 rated Critical, mainly in ANGLE, GPU and WebGL; those CVE ids (e.g. CVE-2026-95350) are distinct from this advisory's list. The advisory contains no network IOCs, malware or actor attribution, so the IOC set here consists of affected product, version and component indicators for exposure and patch-compliance hunting.
MITRE ATT&CK techniques by tactic:
Execution
T1203 Exploitation for Client Execution; T1204.001 User Execution: Malicious Link
Impact
T1499.004 Endpoint Denial of Service: Application or System Exploitation
Remediation
Patches
- Microsoft Edge Stable 154.0.4258.53 (released 2026-10-01)
Immediate actions
- Update Microsoft Edge to 154.0.4258.53 or later on all endpoints
- Restart Edge after the update so the patched build is loaded
Workarounds
- No vendor workaround stated in the advisory; patching is the recommended action
Longer-term hardening
- Enforce Edge auto-update and monitor browser version compliance in endpoint inventory
- Track Microsoft Security Update Guide and Chrome Releases for Chromium-sourced fixes
Affected and fixed versions
- Microsoft — Microsoft Edge (Chromium-based, Stable)
Vulnerable versions: prior to 154.0.4258.53
Fixed in: 154.0.4258.53 - Google — Chromium / Google Chrome (upstream source of the CVEs per NVD)
Vulnerable versions: prior to 152.0.7977.82 (CVE-2026-85047, iOS); prior to 153.0.8010.36; prior to 153.0.8010.52 (CVE-2026-93372, CVE-2026-93380)
Fixed in: 152.0.7977.82; 153.0.8010.36; 153.0.8010.52
Timeline
- Edge 152.0.4191.62 released fixing CVE-2026-85046, flagged exploited in the wild; this CVE is NOT in the A26-10-03 list.
- Edge 152.0.4191.66 released fixing CVE-2026-87491 (exploited in the wild) and Edge-specific CVE-2026-85892; neither is in the A26-10-03 list.
- Chrome 153 reaches Stable (153.0.8010.36/.37) with 230 security fixes, five rated Critical (four in WebGL, one in Cast); the WebGL fixes align with the Chromium-sourced CVEs in this advisory.
- Microsoft Edge Stable 153.0.4234.32 released with the Chromium 153 security updates.
- Chrome 154 reaches Stable (154.0.8037.57/.58) with 108 security fixes, 11 rated Critical (ANGLE, GPU, WebGL); no in-the-wild exploitation reported.
- Microsoft Edge Stable 154.0.4258.37 released, the first Edge 154 build, with the latest Chromium security updates.
- Chrome 154 follow-up update (154.0.8037.92/.93) reported to fix 32 more security issues including a Critical ANGLE buffer overflow (CVE-2026-102331); not in this advisory's CVE list.
- Microsoft Edge Stable 154.0.4258.48 released, the build preceding 154.0.4258.53.
- Microsoft releases Edge Stable 154.0.4258.53 incorporating the latest Chromium security updates; release notes list no CVEs yet and no exploited-in-the-wild flag.
- Hong Kong GovCERT publishes Security Alert A26-10-03 listing 37 CVEs fixed in Edge 154.0.4258.53 and urging users to update.
Sources cited
- HK GovCERT Security Alert (A26-10-03): Multiple Vulnerabilities in Microsoft Edge govcert.gov.hk · Advisory · 2026-10-02
- NVD - CVE-2026-85047 NVD (NIST) · Advisory · 2026-10-02
- NVD - CVE-2026-87438 NVD (NIST) · Advisory · 2026-10-02
- NVD - CVE-2026-93372 NVD (NIST) · Advisory · 2026-10-02
- CISA Known Exploited Vulnerabilities Catalog CISA · Government advisory · 2026-10-02
- Microsoft Edge Release Notes (Security) - October 01, 2026 Microsoft · Vendor report · 2026-10-01
- Microsoft Security Update Guide Microsoft Security Response Center · Vendor report · 2026-10-01
- Chrome Releases - Stable Channel Update for Desktop chromereleases.googleblog.com · Vendor report · 2026-10-01
- Update Chrome: 108 security fixes for desktop, new release for Android (Malwarebytes) malwarebytes.com · News · 2026-09-23
- Chrome 153 Stable Arrives With 230 Security Fixes technobezz.com · News · 2026-09-09
- Google Chrome 154 Fixes 108 Security Flaws: 11 Are Rated Critical (TechRepublic) techrepublic.com · News · 2026-09-23
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.