🛡️ JLSEC-2025-8 — openssh-jll
Description
ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code...
ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability none.
Affected software
JLSEC-2025-8 is recorded against 1 package.
- openssh-jll
Timeline and source
Published on 9 October 2025 and last revised on 25 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
cert-portal.siemens.com (Web)
github.com (Web)
marc.info (Web)
nvd.nist.gov (Web)
www.openssh.com (Web)
www.openwall.com (Web)
Details
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| openssh-jll | — | — |
References
Similar Threats
- Unknown JLSEC-2026-75
- Unknown JLSEC-2026-76
- Unknown JLSEC-2026-77
- Unknown JLSEC-2026-63
- Unknown JLSEC-2026-64
More JLSEC 2025 advisories
Browse all of JLSEC 2025 in the advisory index.
Free Vulnerability Check
Is your site affected by JLSEC-2025-8?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against JLSEC-2025-8 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.