Answer in brief
CVE-2026-70409 records a Unknown severity vulnerability in eldap does not bound the port component of a referral URL before integer conversion. The current sources do not mark it as known exploited. The current feed maps Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Erlang/OTPgeneric | >=17.0 <27.3.4.17 || >=28.0 <28.5.0.6 || >=29.0 <29.0.6 | 27.3.4.17, 28.5.0.6, 29.0.6 |
| Erlang/OTPgeneric | >=1.0.3 <1.2.14.2 || >=1.2.15 <1.2.16.1 || >=1.3 <1.3.1 | 1.2.14.2, 1.2.16.1, 1.3.1 |
| Erlang/OTPgeneric | >=d8dbf15de4fa1a08b9a05e7d8e08fdb025fe1dc3 <* | * |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP eldap allows a malicious or compromised LDAP server to degrade availability by returning a referral URL whose port component is a very long run of digits. eldap:parse_port/2 passes the port substring straight to list_to_integer/1 with no length bound. The surrounding try ... catch only rejects a value that fails to parse, so a syntactically valid port of up to roughly 1.26 million digits converts successfully and costs the caller hundreds of milliseconds of arbitrary-precision arithmetic per referral. The conversion function itself is documented to accept integers of any size, so bounding the input is the caller's responsibility. Reaching the flaw requires the application to pass a server-supplied referral to eldap:parse_ldap_url/1, which eldap never calls itself: referral strings are returned to the caller unparsed. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to eldap from 1.0.3 before 1.2.14.2, from 1.2.15 before 1.2.16.1, and from 1.3 before 1.3.1.
Quoted source text, attributed separately from HOL analysis.