Local file overwrite via symlinked PID path
Published Jun 23, 2025 · Updated Aug 1, 2026
Link following in sslh before 2.2.2 allows local users to overwrite files through a symbolic link at the configured PID-file path. write_pid_file() passed the configured path to fopen() with write-and-truncate mode, so the operating system followed a preexisting symlink to its target. Exploitation requires local access to place the link and a privileged sslh launch that writes that PID file; the maintainer disputes privilege escalation because sslh does not change file ownership.
Summary
What happened
Link following in sslh before 2.2.2 allows local users to overwrite files through a symbolic link at the configured PID-file path. write_pid_file() passed the configured path to fopen() with write-and-truncate mode, so the operating system followed a preexisting symlink to its target. Exploitation requires local access to place the link and a privileged sslh launch that writes that PID file; the maintainer disputes privilege escalation because sslh does not change file ownership.
The record
- CVE
- CVE-2025-52936
- Published
- Jun 23, 2025
- Updated
- Aug 1, 2026
- Vendor
- Yves Rutschle
- Product
- sslh
- Classifications
- CWE-59
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2025CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo