# CVE-2025-52936: Improper Link Resolution Before File Access vulnerability in yrutschle/sslh

> An attacker can exploit improper link resolution to access or modify files outside the intended directory in sslh.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/S:N/AU:Y/R:U/V:C/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2025
- **Updated:** 1 Aug 2026
- **Also known as:** DEBIAN-CVE-2025-52936, DLA-4238-1, GHSA-7wr7-q3ph-825q, UBUNTU-CVE-2025-52936, USN-8360-1

## What is CVE-2025-52936?

CVE-2025-52936 is a critical path traversal vulnerability in yrutschle sslh, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Link Resolution Before File Access ('Link Following') vulnerability in yrutschle sslh.This issue affects sslh: before 2.2.2.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

Upgrade to a fixed version.

## Is CVE-2025-52936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52936 is a critical path traversal vulnerability in yrutschle sslh, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52936 in the wild and no public exploit code.

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

## Sources

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

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