CVE-2026-48860

Distribution-over-TLS LAN allowlist silently bypassed due to sockname/peername confusion in inet_tls_dist

MEDIUM
6.5
CVSS Score
Published: June 10, 2026 at 02:35 PM UTC
Updated: October 26, 2026 at 11:10 AM UTC
2 products affected across 1 vendorErlang /otpErlang /ssl

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
MEDIUM6.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Reliance on IP Address for Authentication vulnerability in Erlang/OTP ssl (inet_tls_dist module) allows unauthenticated bypass of the distribution-over-TLS LAN allowlist. The inet_tls_dist:check_ip/1 function, which enforces a LAN allowlist for Erlang distribution over TLS, calls inet:sockname/1 instead of inet:peername/1 to obtain the peer's IP address. Because inet:sockname/1 returns the local socket address, both the local IP and the supposed peer IP resolve to the same value, causing the subnet mask comparison to always succeed regardless of the actual remote address. Any holder of a CA-signed TLS certificate can therefore bypass the LAN restriction and gain full Erlang distribution access to the node, including rpc:call/4 and code:load_binary/3. This vulnerability is associated with program file lib/ssl/src/inet_tls_dist.erl. This issue affects OTP from OTP 26.0 before 29.0.2, 28.5.0.2 and 27.3.4.13 corresponding to ssl from 11.0 before 11.7.2, 11.6.0.2 and 11.2.12.9.

Affected

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

26.0 ≤ v < 27.3.4.1328.0 ≤ v < 28.5.0.229.0 ≤ v < 29.0.211.026.07a08c5507862a7011568506d0c17b1fdef30bee4
Vendor states this is fixed in 0209a6df65d605552b378273027b3968b35f26b4 (fixed)
Affected range stops below 27.3.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.2, so it looks safe — our inference, not a vendor statement
11.0 ≤ v < 11.2.12.911.6 ≤ v < 11.6.0.211.7 ≤ v < 11.7.2
Affected range stops below 11.2.12.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.6.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.7.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 automatableTotal 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
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-1025CWE-863

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