dbcve.org
Erlang\/otpApplication · Erlang

CVE-2026-48860

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 11.2.12.9 / 11.6.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 OTP 29.0.2, OTP 28.5.0.2 and OTP 27.3.4.13, corresponding to ssl from 11.0 before 11.7.2, 11.6.0.2 and 11.2.12.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-863

An authorization check exists but is flawed, so it passes when it should fail. Attackers probe roles and object references to find the gap. Remediation means centralising and correctly implementing the access-control logic, then testing it against every role.

General guidance for the incorrect authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Erlang\/otpApplication
Affected:>= 26.0, < 27.3.4.13>= 28.0, < 28.5.0.2>= 29.0, < 29.0.2
Erlang\/sslApplication
Affected:>= 11.0, < 11.2.12.9>= 11.6, < 11.6.0.2>= 11.7, < 11.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.2.12.9 / 11.6.0.2 / 11.7.2 or later
Fixed in 11.2.12.911.6.0.211.7.2
Vendor patch github.com →
Recommended fix High confidence

OTP 29.0.2 (or latest stable in your major version line: 27.3.4.13, 28.5.0.2, or 29.0.2)

  1. 1. Identify the current Erlang/OTP version by running 'erl -eval 'erlang:display(erlang:system_info(otp_release)), halt().' -noshell'
  2. 2. Based on your current major version (26, 27, 28, or 29), upgrade to the corresponding fixed release: OTP 27.3.4.13, OTP 28.5.0.2, or OTP 29.0.2
  3. 3. If using a package manager (apt, yum, brew, etc.), update to the latest available package for your OTP version line
  4. 4. Alternatively, rebuild from source using the specific tag: OTP_27.3.4.13, OTP_28.5.0.2, or OTP_29.0.2
  5. 5. Verify the fix by confirming inet_tls_dist:check_ip/1 now uses inet:peername/1 instead of inet:sockname/1
  6. 6. Restart any Erlang nodes that use distribution over TLS with the inet_tls_dist module
Caveat Minor: This is a bugfix release; verify custom ssl distribution configurations still work after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data