---
title: CVE-2026-111497 Node2Shell exploitation detected
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > CVE-2026-111497 Node2Shell exploitation
  detected
---

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

# CVE-2026-111497 Node2Shell exploitation detected
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 %}

Detect exploitation of CVE-2026-111497 (Node2Shell), a Node.js brotli decompression vulnerability that enables remote code execution.

## Strategy{% #strategy %}

The exploit corrupts memory during brotli decompression and redirects the Node.js process into `execve`, replacing itself with an attacker-chosen program under the same PID. Normal `child_process` use forks first, so an in-place exec by `node` is unusual.

- **Critical:** `node` replaced itself via exec within 5 minutes of the public PoC's brotli stream being received on the same host.
- **High:** `node` replaced itself via exec with no exploit stream seen. Covers variants that change the stream, and TLS-terminated traffic the Agent can't inspect.
- **Medium:** The exploit stream was received on the host, with no exec yet. Fires once per host per 5 minutes.

The stream match is specific to the public PoC and only works on cleartext IPv4 traffic at the host. Its process attribution is the sending side (for example `docker-proxy` or an ingress proxy), not the targeted `node` process.

## Triage and response{% #triage-and-response %}

1. Identify the affected workload from `@container.id`, `host`, and `@process.ancestors`. For stream-only signals, map the destination port to the service.
1. Check `@process.executable.path` and `@process.args` for what `node` executed, and look for outbound connections from that process.
1. Confirm the Node.js version is affected by CVE-2026-111497.
1. Isolate the host or terminate the container, then patch Node.js.
1. Until patched, reject `Content-Encoding: br` request bodies at the ingress or service mesh.

*Requires Agent version 7.68 or greater.*
