# CVE-2026-39197: Denial of service in n/a

> Attackers can cause a Denial of Service in Datadog Vector via crafted requests to the prelude endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-44gc-6mm4-5h7r

## What is CVE-2026-39197?

CVE-2026-39197 is a medium-severity denial of service vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in the /util/http/prelude.rs endpoint of Datadog, Inc Vector v0.54.0 allows attackers to cause a Denial of Service (DoS) via a crafted request or payload.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

No fix has been published for CVE-2026-39197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-39197 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39197 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39197 is a medium-severity denial of service vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39197 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-39197/ (Markdown: https://insights.sbomify.com/CVE-2026-39197/index.md)
```

## Sources

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

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