CVE-2026-53422

SFTP REALPATH path-existence oracle allowing filesystem enumeration outside configured root

MEDIUM
4.3
CVSS Score
Published: July 2, 2026 at 04:06 PM UTC
Updated: October 25, 2026 at 09: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
MEDIUM4.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Observable Response Discrepancy vulnerability in Erlang OTP ssh (ssh_sftpd module) allows an authenticated SFTP user to enumerate the existence of files and directories outside the configured root directory. The SSH_FXP_REALPATH handler in ssh_sftpd calls relate_file_name/3 with Canonicalize=false, unlike every other SFTP operation handler. This allows .. components in the requested path to bypass the is_within_root/2 check without being resolved. The un-canonicalized path then enters resolve_symlinks/2, which walks up the directory tree above the configured root and issues read_link() syscalls on arbitrary filesystem paths. An authenticated SFTP client can exploit this by sending a REALPATH request with a crafted traversal path. The server response differs depending on whether the target path exists on the host filesystem (SSH_FXP_NAME when the path resolves successfully, SSH_FX_NO_SUCH_FILE when it does not). This creates a path-existence oracle that an attacker can use to enumerate the filesystem structure outside the configured root, including the existence of sensitive files, directories, and mount points. The vulnerability leaks only the existence of paths. No file contents, credentials, or write access are obtainable through this issue alone. The information gained may assist further attacks when combined with other vulnerabilities. This vulnerability is associated with program files lib/ssh/src/ssh_sftpd.erl and program routine ssh_sftpd:handle_op/4. This issue affects OTP from OTP 17.0 until OTP 29.0.3, 28.5.0.3, and 27.3.4.14 corresponding to ssh from 3.0.1 until 6.0.2, 5.5.2.2, and 5.2.11.9.

Affected

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

17.0 ≤ v < 27.3.4.1428.0 ≤ v < 28.5.0.329.0 ≤ v < 29.0.317.03.0.184adefa331c4159d432d22840663c38f155cd4c1
Affected range stops below 27.3.4.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.3, so it looks safe — our inference, not a vendor statement
3.0.1 ≤ v < 5.2.11.95.3 ≤ v < 5.5.2.26.0 ≤ v < 6.0.2
Affected range stops below 5.2.11.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.2.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.2, so it looks safe — our inference, not a vendor statement

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
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-204

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