Quick answers
- Is CVE-2026-48860 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48860 being exploited in the wild.
- How severe is CVE-2026-48860?
- Informational severity, with a CVSS score of 7.5, published 10 June 2026.
- Which products and versions are affected?
- Erlang/OTP OTP ssl 26.0 to 27.3.4.12, 28.0 to 28.5.0.1, 29.0 to 29.0.1.
- Is there a fix for CVE-2026-48860?
- A patch was published on 2026-06-10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48860 attacked?
- It is attacked from the adjacent network, in a software library.
- Am I affected by CVE-2026-48860?
- Check whether you run Erlang/OTP OTP ssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A logic error in the inet_tls_dist:check_ip/1 function causes a failure in LAN allowlist enforcement for Erlang distribution over TLS. The function incorrectly calls inet:sockname/1 (local address) instead of inet:peername/1 (remote address) to identify the connecting peer. Consequently, the subnet mask comparison compares the local IP against itself, always succeeding regardless of the actual remote IP. An attacker with a valid CA-signed TLS certificate can bypass the LAN restriction to gain full Erlang distribution access, enabling remote code execution via rpc:call/4. This affects OTP 26.0 through versions prior to 29.0.2, 28.5.0.2, and 27.3.4.13.
Affected products
- Erlang OTP/ssl 26.0 to 27.3.4.12, 28.0 to 28.5.0.1, 29.0 to 29.0.1
Timeline
- 2026-06-10: disclosed
- 2026-06-10: advisory
- 2026-06-10: patched