CVE-2026-49252 Microsoft Sentinel · KQL

Detect Prototype Pollution in @deepstream/server (CVE-2026-49252) in Microsoft Sentinel

CVE-2026-49252 is a critical prototype pollution vulnerability (CVSS 9.9) in @deepstream/server versions prior to 10.0.5. An attacker can manipulate JavaScript object prototypes via crafted deepstream messages, potentially leading to remote code execution, privilege escalation, or denial of service within the Node.js server process.

MITRE ATT&CK

Tactic
Initial Access Execution Privilege Escalation

KQL Detection Query

Microsoft Sentinel (KQL)
kusto
union DeviceNetworkEvents, DeviceProcessEvents
| where TimeGenerated > ago(24h)
| where (ProcessCommandLine has "deepstream" or ProcessCommandLine has "@deepstream/server")
    or (InitiatingProcessCommandLine has "deepstream")
| extend SuspiciousPayload = iff(
    ProcessCommandLine has "__proto__" or ProcessCommandLine has "constructor" or ProcessCommandLine has "prototype",
    true, false
)
| project TimeGenerated, DeviceName, AccountName, ProcessCommandLine, InitiatingProcessCommandLine, RemoteIP, RemotePort, SuspiciousPayload
| order by TimeGenerated desc
critical severity medium confidence

Detects process and network activity associated with deepstream server processes, flagging command lines or spawned children that contain prototype pollution indicators (__proto__, constructor, prototype).

Data Sources

Microsoft Defender for EndpointMicrosoft Sentinel DeviceProcessEventsDeviceNetworkEvents

Required Tables

DeviceProcessEventsDeviceNetworkEvents

False Positives & Tuning

  • Legitimate deepstream administrative scripts referencing prototype keywords in benign contexts
  • Security scanning tools probing deepstream endpoints for vulnerability assessment
  • Development environments running test suites that exercise prototype manipulation code paths

Other platforms for CVE-2026-49252


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 1Deepstream Prototype Pollution via Crafted Client Message

    Expected signal: Node.js application logs should show receipt of a record set message with __proto__ key; process monitoring may show unexpected property on Object.prototype after message processing

  2. Test 2deepstream Server Version Enumeration

    Expected signal: Process execution event for node reading package.json; stdout output containing version string below 10.0.5 confirms vulnerability

  3. Test 3Prototype Pollution Object Property Verification

    Expected signal: Node.js process execution with inline script; stdout output 'YES - VULNERABLE' confirms Object.prototype susceptibility

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections