# CVE-2024-28995: SolarWinds Serv-U Path Traversal Vulnerability

> Attackers can exploit a directory traversal flaw in SolarWinds Serv-U to read sensitive files on the host machine.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 17 Jul 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gr87-q8xh-gq3c

## What is CVE-2024-28995?

CVE-2024-28995 is a high-severity path traversal vulnerability in Solarwinds Serv-U, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SolarWinds Serv-U was susceptible to a directory transversal vulnerability that would allow access to read sensitive files on the host machine.

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

## Which versions are affected by CVE-2024-28995?

It affects 1 product.


Products: Solarwinds Serv-U.

## How do I fix CVE-2024-28995?

No fix has been published for CVE-2024-28995 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Aug 2024.

## Is CVE-2024-28995 being exploited?

Yes. Attackers have exploited CVE-2024-28995 in the wild since at least 17 Jul 2024.

Public exploit code:

- CVE-2024-28955 Exploitation PoC  (github_poc): https://github.com/Stuub/CVE-2024-28995
- CVE-2024-28995 POC Vulnerability Scanner (github_poc): https://github.com/bigb0x/CVE-2024-28995
- SolarWinds Serv-U was susceptible to a directory transversal vulnerability that would allow access to read sensitive files on the host machine.  (github_poc): https://github.com/gotr00t0day/CVE-2024-28995
- https://github.com/ggfzx/CVE-2024-28995 (github_poc): https://github.com/ggfzx/CVE-2024-28995
- Exploit for CVE-2024-28995 (github_poc): https://github.com/0xc4t/CVE-2024-28995
- https://github.com/huseyinstif/CVE-2024-28995-Nuclei-Template (github_poc): https://github.com/huseyinstif/CVE-2024-28995-Nuclei-Template

## Other vulnerabilities in Solarwinds Serv-U

- [CVE-2021-35211](https://insights.sbomify.com/CVE-2021-35211/): SolarWinds Serv-U Remote Code Execution (critical 9.0, exploited in the wild)
- [CVE-2026-28318](https://insights.sbomify.com/CVE-2026-28318/): SolarWinds Serv-U Uncontrolled Resource Consumption (high 7.5, exploited in the wild)
- [CVE-2021-35247](https://insights.sbomify.com/CVE-2021-35247/): SolarWinds Serv-U Improper Input Validation (medium 4.3, exploited in the wild)
- [CVE-2020-35481](https://insights.sbomify.com/CVE-2020-35481/): Code injection in n/a (critical 9.8)
- [CVE-2026-28302](https://insights.sbomify.com/CVE-2026-28302/): SolarWinds Serv-U Insecure Direct Object Reference (IDOR) Vulnerability (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28995 and fix it if it is affected.

What it is: CVE-2024-28995 is a high-severity path traversal vulnerability in Solarwinds Serv-U, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-28995 in the wild since at least 17 Jul 2024.

Affected product: Solarwinds Serv-U. 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-2024-28995/ (Markdown: https://insights.sbomify.com/CVE-2024-28995/index.md)
```

## Sources

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

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