Security Resilience

CVE-2026-28810

Erlang\/Otp 17.0 – 26.2.5.19

Published
07 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0027 19th percentile
Risk Priority 31 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-28810 is a medium-severity Generation of Predictable Numbers or Identifiers (CWE-340) vulnerability in Erlang\/Otp. Its CVSS base score is 6.3 (Medium).

Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Generation of Predictable Numbers or Identifiers vulnerability in Erlang/OTP kernel (inet_res, inet_db modules) allows DNS Cache Poisoning. The built-in DNS resolver (inet_res) uses a sequential, process-global 16-bit transaction ID for UDP queries and does not implement source port randomization. Response…

more

validation relies almost entirely on this ID, making DNS cache poisoning practical for an attacker who can observe one query or predict the next ID. This conflicts with RFC 5452 recommendations for mitigating forged DNS answers. inet_res is intended for use in trusted network environments and with trusted recursive resolvers. Earlier documentation did not clearly state this deployment assumption, which could lead users to deploy the resolver in environments where spoofed DNS responses are possible. This vulnerability is associated with program files lib/kernel/src/inet_db.erl and lib/kernel/src/inet_res.erl. This issue affects OTP from OTP 17.0 before OTP 28.4.2, OTP 27.3.4.10 and OTP 26.2.5.19, corresponding to kernel from 3.0 before 10.6.2, 10.2.7.4 and 9.2.4.11.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-42789Same product: Erlang Erlang\/Otp
CVE-2026-42790Same product: Erlang Erlang\/Otp
CVE-2026-42791Same product: Erlang Erlang\/Otp
CVE-2026-54890Same product: Erlang Erlang\/Otp
CVE-2026-59251Same product: Erlang Erlang\/Otp
CVE-2026-55953Same product: Erlang Erlang\/Otp
CVE-2026-48856Same product: Erlang Erlang\/Otp
CVE-2026-55952Same product: Erlang Erlang\/Otp
CVE-2026-54887Same product: Erlang Erlang\/Otp
CVE-2026-53422Same product: Erlang Erlang\/Otp

Affected Assets

erlang
erlang\/otp
17.0 — 26.2.5.19 · 27.0 — 27.3.4.10 · 28.0 — 28.4.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover predictable number generation through targeted analysis or fuzzing of identifier creation routines.

Cryptographic key establishment and management mandates proper entropy and randomness during generation, directly stopping predictable identifiers at the source.

Authenticator management requires secure initial distribution and handling of authenticators, structurally preventing predictable values from being usable.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Cryptographic controls require use of approved, sufficiently random algorithms and key-generation methods, directly mitigating predictable number/identifier weaknesses.

finds

Security testing in development can detect predictable identifiers through static/dynamic analysis and fuzzing, reducing residual risk.

prevents

Secure-coding standards explicitly forbid predictable random functions and mandate cryptographically secure RNGs, preventing the weakness at the source.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-340, a class-level weakness. Rules are authored against its narrower children: CWE-342, CWE-343.

References