# CVE-2025-39665: Livestatus Injection in dynmaps

> An unauthenticated attacker can enumerate Checkmk usernames via user enumeration in Nagvis' Checkmk MultisiteAuth.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-39665, GHSA-2x34-p5xr-4cq8, UBUNTU-CVE-2025-39665

## What is CVE-2025-39665?

CVE-2025-39665 is a medium-severity vulnerability in Nagvis, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User enumeration in Nagvis' Checkmk MultisiteAuth before version 1.9.48 allows an unauthenticated attacker to enumerate Checkmk usernames.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2025-39665?

It affects 1 product.


Products: Nagvis Nagvis.

## How do I fix CVE-2025-39665?

Upgrade to a fixed version.

## Is CVE-2025-39665 being exploited?

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

## Other vulnerabilities in Nagvis

- [CVE-2022-46945](https://insights.sbomify.com/CVE-2022-46945/): Path traversal in n/a (critical 9.1)
- [CVE-2024-47093](https://insights.sbomify.com/CVE-2024-47093/): Fix various XSS issues and potential RCE (high 8.8)
- [CVE-2021-33178](https://insights.sbomify.com/CVE-2021-33178/): Path traversal in NagVis (medium 6.5)
- [CVE-2023-46287](https://insights.sbomify.com/CVE-2023-46287/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-6393](https://insights.sbomify.com/CVE-2017-6393/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-39665 and fix it if it is affected.

What it is: CVE-2025-39665 is a medium-severity vulnerability in Nagvis, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-39665 in the wild and no public exploit code.

Affected product: Nagvis. 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-2025-39665/ (Markdown: https://insights.sbomify.com/CVE-2025-39665/index.md)
```

## Sources

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

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