OESA-2026-2941 (CVE-2026-32147)
Vulnerability from osv_openeuler – Published: 2026-07-09 11:11 – Updated: 2026-08-06 11:11 – Source websiteErlang is a general-purpose programming language and runtime environment. Erlang has built-in support for concurrency, distribution and fault tolerance. Erlang is used in several large telecommunication systems from Ericsson.
Security Fix(es):
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.(CVE-2026-32147)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"erlang-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-asn1-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-common_test-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-compiler-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-crypto-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-debugger-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-debuginfo-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-debugsource-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-dialyzer-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-diameter-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-edoc-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-eldap-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-erl_docgen-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-erl_interface-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-erts-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-et-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-eunit-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-examples-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-ftp-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-inets-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-jinterface-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-kernel-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-megaco-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-mnesia-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-observer-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-odbc-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-os_mon-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-parsetools-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-public_key-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-reltool-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-runtime_tools-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-sasl-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-snmp-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-src-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-ssh-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-ssl-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-stdlib-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-syntax_tools-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-tftp-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-tools-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-wx-25.3.2.6-17.oe2403sp3.aarch64.rpm",
"erlang-xmerl-25.3.2.6-17.oe2403sp3.aarch64.rpm"
],
"src": [
"erlang-25.3.2.6-17.oe2403sp3.src.rpm"
],
"x86_64": [
"erlang-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-asn1-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-common_test-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-compiler-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-crypto-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-debugger-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-debuginfo-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-debugsource-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-dialyzer-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-diameter-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-edoc-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-eldap-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-erl_docgen-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-erl_interface-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-erts-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-et-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-eunit-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-examples-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-ftp-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-inets-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-jinterface-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-kernel-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-megaco-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-mnesia-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-observer-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-odbc-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-os_mon-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-parsetools-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-public_key-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-reltool-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-runtime_tools-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-sasl-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-snmp-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-src-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-ssh-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-ssl-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-stdlib-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-syntax_tools-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-tftp-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-tools-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-wx-25.3.2.6-17.oe2403sp3.x86_64.rpm",
"erlang-xmerl-25.3.2.6-17.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "erlang",
"purl": "pkg:rpm/openEuler/erlang\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.3.2.6-17.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "Erlang is a general-purpose programming language and runtime environment. Erlang has built-in support for concurrency, distribution and fault tolerance. Erlang is used in several large telecommunication systems from Ericsson.\r\n\r\nSecurity Fix(es):\n\nImproper Limitation of a Pathname to a Restricted Directory (\u0026apos;Path Traversal\u0026apos;) vulnerability in Erlang OTP ssh (ssh_sftpd module) allows an authenticated SFTP user to modify file attributes outside the configured chroot directory.\n\nThe 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.\n\nAny 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.\n\nIf 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.\n\nThis 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.\n\nThis 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.(CVE-2026-32147)",
"id": "OESA-2026-2941",
"modified": "2026-08-06T11:11:50Z",
"published": "2026-07-09T11:11:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2941"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32147"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "erlang security update",
"upstream": [
"CVE-2026-32147"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.