CVE-2026-48859
Erlang\/Otp 29.0 – 29.0.2
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-48859 is a medium-severity Observable Timing Discrepancy (CWE-208) vulnerability in Erlang\/Otp. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Discovery (T1083); ranked at the 29th 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 SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-36054
Vulnerability Data
Observable Timing Discrepancy vulnerability in Erlang/OTP ssh (ssh_auth, ssh_options modules) allows unauthenticated remote username enumeration via timing side-channel in password authentication. When the SSH daemon is configured with the user_passwords or password option, ssh_auth:check_password/3 performs a PBKDF2-SHA256 computation with 600,000…
more
iterations (~300ms) for valid usernames, but returns immediately (~0ms) for invalid usernames via the ssh_options:get_password_option/2 path. This timing difference is detectable in a single authentication attempt and allows an unauthenticated attacker to distinguish valid from invalid usernames. The user_passwords and password options are documented as intended for test purposes; the recommended alternative is pwdfun, which is not affected by this vulnerability. This vulnerability is associated with program files lib/ssh/src/ssh_auth.erl and lib/ssh/src/ssh_options.erl. This issue affects OTP from OTP 29.0 before OTP 29.0.2, corresponding to ssh from 6.0 before 6.0.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.2.4
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.
Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.
Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's SOURCE reach (code review, static analysis) catches obvious non-constant-time comparisons and early-exit loops in security-sensitive code, and its RUNTIME reach (penetration testing) can surface some timing discrepancies under focused timing analysis, but many timing side channels are too subtle for standard code review, evade static-analysis pattern matching, and require specialised statistical timing measurement that ordinary pen testing does not perform — a nameable remainder that keeps the grade at `partial`.
A.8.5 items (c) and (d) directly address timing-based information disclosure during log-on — not indicating which part of the data is correct/incorrect, and validating log-on information only on completion of all input — which blocks the byte-by-byte password comparison and differential-error timing attacks documented in CWE-208's observed examples; however, the clause does not reach timing discrepancies in cryptographic operations (HMAC comparison, padding checks) or other authentication-related timing side channels beyond the log-on procedure itself.
A.8.8's reach is DISCLOSURE — it finds CWE-208 only where a vendor has published a CVE for a timing discrepancy in software present in the asset inventory and a scanner flags it. Several CWE-208 instances do surface as CVEs (CVE-2019-10071, CVE-2014-0984, CVE-2003-0078, etc.), so the class commonly discloses, but most timing discrepancies in custom or unexamined code are never published, capping the grade at `partial` under the disclosure-reach ceiling.