Skip to main content
Menu
CVEs

IDNA denial of service in punycode label decoding

CVE-2026-117678Published November 19, 2026, updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 8.0.0
Who is exposed
Not reported

Summary

The idna library can be made to use excessive CPU time. A local attacker who controls a hostname passed to the library, with no login or user action needed, can exhaust processing resources by supplying a hostname with an over-long xn-- label, since the library decodes such labels before checking their length.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 8.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-117678 (idna: punycode labels are decoded before the 63-octet length check, so a long xn-- label causes super-linear CPU use), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-117678 (entry last updated 2026-11-19):
Affected:
- Hex package idna: from 0.5.0, fixed in 8.0.0
- benoitc idna: version range not reported
Fixed versions: 8.0.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-117678 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-117678 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Hex): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/benoitc/erlang-idna/pull/45
- https://github.com/benoitc/erlang-idna/commit/7a465b630eb793556aa7ac282fb73e49251dadd2
- https://github.com/benoitc/erlang-idna/pull/44
- https://cna.erlef.org/cves/CVE-2026-117678.html
- https://osv.dev/vulnerability/EEF-CVE-2026-117678
- https://github.com/benoitc/erlang-idna/commit/c8caba6653259071f7076fe49320f37402b8b81f
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-117678
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-117678"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Hex packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-117678

Is CVE-2026-117678 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-117678?

idna (Hex): from 0.5.0 before 8.0.0.

Source: cve.now feed data

How do I fix CVE-2026-117678?

Upgrade to a fixed version: 8.0.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.