Answer in brief
CVE-2026-117678 records a Medium severity (CVSS 6.9) vulnerability in idna: punycode labels are decoded before the 63-octet length check, so a long xn-- label causes super-linear CPU use. The current sources do not mark it as known exploited. The current feed maps benoitc/benoitc/erlang-idna (generic), benoitc/idna (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.9. 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 benoitc/benoitc/erlang-idna (generic), benoitc/idna (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| benoitc/benoitc/erlang-idnageneric | >=c8caba6653259071f7076fe49320f37402b8b81f <7a465b630eb793556aa7ac282fb73e49251dadd2 | 7a465b630eb793556aa7ac282fb73e49251dadd2 |
| benoitc/idnageneric | >=0.5.0 <8.0.0 | 8.0.0 |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 19, 2026
Inefficient Algorithmic Complexity vulnerability in benoitc idna allows an attacker who controls a hostname passed to the library to exhaust CPU via an over-long xn-- label. idna:ulabel/1 in src/idna.erl hands every ASCII label that starts with xn-- to punycode:decode/1 without applying check_label_length/1, the 63-octet DNS label limit. punycode:decode/1 in src/punycode.erl builds its output with list appends in insert/4, so its cost grows super-linearly with the label length. A label of a few kilobytes keeps a scheduler busy for seconds to minutes before the label is rejected as invalid punycode. Every decode entry point reaches this path: decode/1, decode/2, to_unicode/1 and from_ascii/1. The encode path reaches it as well, because alabel/1 calls ulabel/1 on an ASCII xn-- label before its own length check, so encode/1, encode/2 and to_ascii/1 are affected for such input. This issue affects idna: from 0.5.0 before 8.0.0.
Quoted source text, attributed separately from HOL analysis.