CVE-2026-87081
HIGHDescription
Net::IDN::UTS46 versions before 2.590 for Perl allow CPU exhaustion via quadratic punycode encoding of an overlong label before the length check in to_ascii. to_ascii punycode encodes each label and only then applies the 63-byte DNS limit. encode_punycode in both backends follows the sample implementation in RFC 3492, whose outer loop runs once per distinct non-ASCII code point and scans the whole input each round, so a label of distinct non-ASCII characters costs the square of its length before the limit rejects it. Every ASCII conversion in the distribution, including domain_to_ascii and email_to_ascii, goes through to_ascii.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 49% of all known CVEs.
References
Related Vulnerabilities
Other CWE-407 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-27223 | Medium | 5.2 | 78% | - | Fix |
| CVE-2022-36021 | Medium | 5.5 | 60% | - | Fix |
| CVE-2021-33582 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-43485 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-43484 | High | 7.5 | 3.0% | - | Fix |
| CVE-2016-10396 | High | 7.5 | 2.9% | - | - |
Common questions
How do I fix CVE-2026-87081?
No published fix for CVE-2026-87081 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-87081 being actively exploited?
Not that we know of. CVE-2026-87081 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.63% is the estimated probability that it will be exploited in the next 30 days. That is higher than 49% of all scored CVEs.
How severe is CVE-2026-87081?
CVE-2026-87081 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-87081
Markdown
[](https://tridentstack.com/cve/CVE-2026-87081)HTML
<a href="https://tridentstack.com/cve/CVE-2026-87081"><img src="https://tridentstack.com/cve/badge/CVE-2026-87081.svg" alt="CVE-2026-87081"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-22.