# CVE-2026-116693: dd-trace: ReDOS in URL query string obfuscation


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** ECHO-e026-2188-317a, GHSA-x94g-w73q-hpcw

## What is CVE-2026-116693?

CVE-2026-116693 is a high-severity vulnerability in DataDog dd-trace-js, published on 27 Oct 2026. 

### Official description

dd-trace is the Datadog APM client for Node.js. From 2.0.0 until 5.131.1 and 6.20.1, the default DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP can perform excessive backtracking on attacker-controlled URL query strings. The expression is applied synchronously while recording HTTP URL metadata, allowing a crafted request to consume excessive CPU, stall request processing, and make the instrumented application unavailable. This issue is fixed in versions 5.131.1 and 6.20.1.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-116693?

4 open source packages ship an affected version, including dd-trace.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dd-trace` | npm | From 2.0.0 | 5.131.1 |
| `dd-trace` | npm | From 2.0.0 | 5.131.1 |
| `dd-trace` | npm | From 6.0.0 | 6.20.1 |
| `dd-trace` | npm | From 6.0.0 | 6.20.1 |

## How do I fix CVE-2026-116693?

Upgrade dd-trace to a fixed version for your release line: 5.131.1 or 6.20.1.

## Is CVE-2026-116693 being exploited?

There is no known exploitation of CVE-2026-116693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116693 and fix it if it is affected.

What it is: CVE-2026-116693 is a high-severity vulnerability in DataDog dd-trace-js, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116693 in the wild and no public exploit code.

Affected packages and fixed versions:
- dd-trace (npm): affected from 2.0.0; fixed in 5.131.1
- dd-trace (npm): affected from 2.0.0; fixed in 5.131.1
- dd-trace (npm): affected from 6.0.0; fixed in 6.20.1
- dd-trace (npm): affected from 6.0.0; fixed in 6.20.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116693/ (Markdown: https://insights.sbomify.com/CVE-2026-116693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116693
- OSV: https://osv.dev/vulnerability/CVE-2026-116693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116693/
Summaries are generated and may contain mistakes; the official description above is the record.