# CVE-2022-46945: Path traversal in n/a

> Attackers can read arbitrary files from the server via a path traversal flaw in NagVis, potentially exposing sensitive configuration or data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:L/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-46945, GHSA-hw4x-q63w-42vp, UBUNTU-CVE-2022-46945

## What is CVE-2022-46945?

CVE-2022-46945 is a critical path traversal vulnerability in n/a, published on 26 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nagvis before 1.9.34 was discovered to contain an arbitrary file read vulnerability via the component /core/classes/NagVisHoverUrl.php.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-46945?

It affects 1 product.


Products: Nagvis Nagvis.

## How do I fix CVE-2022-46945?

Upgrade to a fixed version.

## Is CVE-2022-46945 being exploited?

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

Public exploit code:

- NagVis 1.9.33 - Arbitrary File Read (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-47093](https://insights.sbomify.com/CVE-2024-47093/): Fix various XSS issues and potential RCE (high 8.8)
- [CVE-2025-39665](https://insights.sbomify.com/CVE-2025-39665/): Livestatus Injection in dynmaps (medium 6.9)
- [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-2022-46945 and fix it if it is affected.

What it is: CVE-2022-46945 is a critical path traversal vulnerability in n/a, published on 26 May 2023. 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-2022-46945 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-2022-46945/ (Markdown: https://insights.sbomify.com/CVE-2022-46945/index.md)
```

## Sources

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

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