# CVE-2026-48855: SFTP READLINK Leaks Absolute Backend Filesystem Path When Root Is Configured

> Authenticated SFTP clients can leak absolute backend filesystem paths via symlink resolution when a chroot root is configured.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 24 Sep 2026
- **Also known as:** AZL-90129, DEBIAN-CVE-2026-48855, EEF-CVE-2026-48855, GHSA-pv7g-pjrq-x2fh, MGASA-2026-0270, UBUNTU-CVE-2026-48855

## What is CVE-2026-48855?

CVE-2026-48855 is a low-severity vulnerability in Erlang OTP, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 OTP 27.3.4.13, OTP 28.5.0.2, and OTP 29.0.2, corresponding to ssh from 3.0.1 before 5.2.11.8, 5.5.2.1, and 6.0.1. Whether OTP before OTP 17.0, corresponding to ssh before 3.0.1, is affected is unknown.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-48855?

It affects 2 products.


Products: Erlang Erlang\/Otp, Erlang Erlang\/Ssh.

## How do I fix CVE-2026-48855?

Apply the vendor's patch.

## Is CVE-2026-48855 being exploited?

There is no known exploitation of CVE-2026-48855 in the wild and no public exploit code.

## Other vulnerabilities in Erlang OTP

- [CVE-2022-37026](https://insights.sbomify.com/CVE-2022-37026/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-10253](https://insights.sbomify.com/CVE-2016-10253/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-55953](https://insights.sbomify.com/CVE-2026-55953/): TLS 1.2 and DTLS client accepts unoffered anonymous cipher suite, bypassing server authentication (critical 9.1)
- [CVE-2026-49759](https://insights.sbomify.com/CVE-2026-49759/): Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash (high 8.8)
- [CVE-2026-58227](https://insights.sbomify.com/CVE-2026-58227/): TLS/DTLS denial of service via unbounded recursion on cross-signed peer certificate chain (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48855 and fix it if it is affected.

What it is: CVE-2026-48855 is a low-severity vulnerability in Erlang OTP, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48855 in the wild and no public exploit code.

Affected product: Erlang OTP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48855/ (Markdown: https://insights.sbomify.com/CVE-2026-48855/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48855
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48855
- OSV: https://osv.dev/vulnerability/CVE-2026-48855

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48855/
Summaries are generated and may contain mistakes; the official description above is the record.