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

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

Published: 2025-06-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-52936 is rated Moderate Risk (52.2/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.20%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-52936

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.05% 0.20% +0.15%
2 2026-01-30 0.01% 0.05% +0.04%
3 2025-06-23 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-52936

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.3 4.0 CRITICAL
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:M/U:Amber Click to expand
Attack vector (AV:L)
Attacker needs local access on the target system.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:L)
Limited availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:H)
High confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:H)
High integrity impact on subsequent systems.
Subsequent system availability impact (SA:L)
Limited availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:N)
Negligible: impact meets the IEC 61508 negligible safety consequence category.
Automatable (supplemental) (AU:Y)
Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated.
Recovery (supplemental) (R:U)
User: manual user intervention is needed to recover services.
Value density (supplemental) (V:C)
Concentrated: a single exploit event controls rich resources (e.g., a central server).
Vulnerability response effort (supplemental) (RE:M)
Moderate effort (remote update, disable subsystem, simple upgrade with minor service impact).
Provider urgency (supplemental) (U:AMBER)
Amber: provider rates moderate urgency.
 — — [email protected]

Weakness enumeration for CVE-2025-52936

OS Trackers for CVE-2025-52936

vendor priority summary link
alpine critical CVE-2025-52936: 1 source package rows (sslh); 6 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 6. https://security.alpinelinux.org/vuln/CVE-2025-52936
debian not yet assigned CVE-2025-52936 not yet assigned priority: Debian including 1 source packages (sslh), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 4, resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-52936
ubuntu medium CVE-2025-52936 medium priority: Ubuntu including 1 source packages (sslh), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2025-52936

Affected software / configurations for CVE-2025-52936

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-52936

cvelogic Threat Intelligence