CVE-2026-117678

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129475 (ENISA EUVD) · GHSA-5pq6-7wm2-5x62 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Advisory Details (6)

Auto-updated Nov 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr.
GitHub commit Patch Available

commit 7a465b630eb7 (benoitc/erlang-idna)

Patch available: benoitc/erlang-idna 8.0.0 (contains commit 7a465b630eb7)

https://github.com/benoitc/erlang-idna/commit/7a465b630eb793556aa7ac282fb73e49251dadd2
GitHub commit Patch Available

commit c8caba665325 (benoitc/erlang-idna)

Patch available: benoitc/erlang-idna 8.0.0 (contains commit c8caba665325)

https://github.com/benoitc/erlang-idna/commit/c8caba6653259071f7076fe49320f37402b8b81f
GitHub pull request Patch Available

Reject over-long labels before Punycode and speed up the transform

Patch available: benoitc/erlang-idna 8.0.0 (PR #45 merged 2026-11-12)

https://github.com/benoitc/erlang-idna/pull/45
Web page🟡 PoC Available

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-117678
Web page🟡 PoC Available

CVE-2026-117678

https://cna.erlef.org/cves/CVE-2026-117678.html
GitHub pull request

Check label length before Punycode and fix the transform's complexity

Upstream fix in progress (PR #44 · benoitc/erlang-idna, state=closed)

https://github.com/benoitc/erlang-idna/pull/44

Vendor Advisories for CVE-2026-117678(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
idna1.0.1 ... 7.1.0 (19 versions)
  • 0.5.0 up to 8.0.0: fixed in 8.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-20 05:14 UTCEchelonGraph re-scored
  4. 2026-11-20 05:14 UTCGHSA enrichmentGHSA-5pq6-7wm2-5x62 · GitHub severity MODERATE
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-19 15:29 UTCEchelonGraph re-scored
  7. 2026-11-19 15:29 UTCGHSA enrichmentGHSA-5pq6-7wm2-5x62 · GitHub severity MODERATE
  8. 2026-11-19 15:03 UTCEchelonGraph re-scored
  9. 2026-11-19 15:03 UTCGHSA enrichmentGHSA-5pq6-7wm2-5x62 · GitHub severity MODERATE
  10. 2026-11-19 07:16 UTCEchelonGraph re-scored
  11. 2026-11-19 07:16 UTCGHSA enrichmentGHSA-5pq6-7wm2-5x62 · GitHub severity MODERATE
  12. 2026-11-19 07:03 UTCENISA EUVD ID recordedEUVD-2026-129475 · Source: ENISA EUVD
  13. 2026-11-19 06:46 UTCGHSA enrichmentGHSA-5pq6-7wm2-5x62 · GitHub severity MODERATE
  14. 2026-11-19 06:28 UTCEchelonGraph re-scored
  15. 2026-11-19 05:43 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  16. 2026-11-19 05:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-117678?
CVE-2026-117678 is a medium-severity vulnerability; its CVE record was published on November 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…
When was CVE-2026-117678 made public?
CVE-2026-117678 was made public on October 25, 2026: that is the date its CVE record's CNA, Erlang Ecosystem Foundation, gives for when the vulnerability was made public. The CVE record itself was published on November 19, 2026. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-117678 actively exploited?
CVE-2026-117678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-117678?
CVE-2026-117678 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-117678?
A fix for CVE-2026-117678 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-117678 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-117678

Explore →

Is Your Infrastructure Affected by CVE-2026-117678?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.