CVE-2026-32147

SFTP chroot bypass via path traversal in SSH_FXP_FSETSTAT

MEDIUM
4.3
CVSS Score
Published: April 21, 2026 at 12:01 PM UTC
Updated: July 24, 2026 at 03:33 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.4%
SSVC
No known exploit

Description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Erlang OTP ssh (ssh_sftpd module) allows an authenticated SFTP user to modify file attributes outside the configured chroot directory. The SFTP daemon (ssh_sftpd) stores the raw, user-supplied path in file handles instead of the chroot-resolved path. When SSH_FXP_FSETSTAT is issued on such a handle, file attributes (permissions, ownership, timestamps) are modified on the real filesystem path, bypassing the root directory boundary entirely. Any authenticated SFTP user on a server configured with the root option can modify file attributes of files outside the intended chroot boundary. The prerequisite is that a target file must exist on the real filesystem at the same relative path. Note that this vulnerability only allows modification of file attributes; file contents cannot be read or altered through this attack vector. If the SSH daemon runs as root, this enables direct privilege escalation: an attacker can set the setuid bit on any binary, change ownership of sensitive files, or make system configuration world-writable. This vulnerability is associated with program files lib/ssh/src/ssh_sftpd.erl and program routines ssh_sftpd:do_open/4 and ssh_sftpd:handle_op/4. This issue affects OTP from OTP 17.0 until OTP 28.4.3, 27.3.4.11, and 26.2.5.20 corresponding to ssh from 3.01 until 5.5.3, 5.2.11.7, and 5.1.4.15.

Affected

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

v ≥ 17.0v ≥ 3.01v < 26.2.5.2017.0 ≤ v < 26.2.5.2027.0 ≤ v < 27.3.4.1128.0 ≤ v < 28.4.317.03.017b8f441ca711f9812fad9e9115bab3c3aa92f79
Affected range stops below 26.2.5.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 27.3.4.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.4.3, so it looks safe — our inference, not a vendor statement
3.0.1 ≤ v < 5.1.4.155.2 ≤ v < 5.2.11.75.5 ≤ v < 5.5.2
Affected range stops below 5.1.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.11.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

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

Quick Info

StatusMODIFIED
CWE
CWE-22

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