CVE-2026-117678: fallo de gravedad media en benoitc idna
idna: punycode labels are decoded before the 63-octet length check, so a long xn-- label causes super-linear CPU use
Publicada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 6.9epss 0.2%
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.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Productos afectados
benoitc · idnaReferencias
https://cna.erlef.org/cves/CVE-2026-117678.htmlhttps://github.com/benoitc/erlang-idna/commit/7a465b630eb793556aa7ac282fb73e49251dadd2https://github.com/benoitc/erlang-idna/commit/c8caba6653259071f7076fe49320f37402b8b81fhttps://github.com/benoitc/erlang-idna/pull/44https://github.com/benoitc/erlang-idna/pull/45https://osv.dev/vulnerability/EEF-CVE-2026-117678