CVE-2026-48855

SFTP READLINK Leaks Absolute Backend Filesystem Path When Root Is Configured

MEDIUM
6.5
CVSS Score
Published: June 10, 2026 at 02:35 PM UTC
Updated: October 25, 2026 at 11:10 PM UTC
2 products affected across 1 vendorErlang /otpErlang /ssh

Using OTP by Erlang?

Get instant alerts when new vulnerabilities affect OTP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Erlang OTP ssh (ssh_sftpd module) allows File Discovery. The SSH_FXP_READLINK handler in ssh_sftpd sends the raw result of file:read_link/2 to the client without calling chroot_filename/2 to strip the backend root prefix. An authenticated SFTP client can create a symlink inside the chroot pointing to /; ssh_sftpd resolves the target to the absolute backend root and stores it on disk. Reading the symlink back via SSH_FXP_READLINK returns that absolute path, for example /data/sftp, instead of the chrooted value /. The information disclosed is the absolute filesystem path of the SFTP root directory and of any symlink targets within it. No file contents, credentials, or access to paths outside the root directory are obtainable through this issue alone. This vulnerability is associated with program files lib/ssh/src/ssh_sftpd.erl. This issue affects OTP from OTP 17.0 before 29.0.2, 28.5.0.2 and 27.3.4.13 corresponding to ssh from 3.0.1 before 6.0.1, 5.5.2.1 and 5.2.11.8.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

17.0 ≤ v < 27.3.4.1328.0 ≤ v < 28.5.0.229.0 ≤ v < 29.0.217.03.0.18225797f7ef943d0c82a1d9dd6650d94ca2580d
Affected range stops below 27.3.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 8f4224a0d2676b0653d2c71a889a956e8c2c62d6 (unaffected)
3.0.1 ≤ v < 5.2.11.85.5 ≤ v < 5.5.2.16.0 ≤ v < 6.0.1
Affected range stops below 5.2.11.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.2.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.1, so it looks safe — our inference, not a vendor statement

References (6)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card