CVE-2026-87082
HIGHDescription
Net::IDN::Punycode versions before 2.590 for Perl hang, crash or return a wrong label via unvalidated malformed UTF-8 in encode_punycode. Neither backend checks that its input is well-formed UTF-8, so a string with the UTF-8 flag set over malformed bytes, as the :utf8 PerlIO layer produces from any malformed input, reaches the encoder unchecked. On perl 5.32 and later the XS backend reports a malformed sequence with a length of `(STRLEN)-1`, so the scan steps back one byte instead of forward and never ends. On earlier perls the XS returns a valid label for a different name. The pure-Perl backend runs a regex over the flagged string. Depending on the bytes, it aborts with SIGBUS on perl 5.28 and later, dies with a panic, or returns a wrong label. The documented conversion functions match the label against Unicode properties first and that match dies on such a string, so only a direct call to encode_punycode reaches the defect. The decoder is not affected. A direct caller encoding attacker-supplied bytes hangs, crashes or gets a label for a name the input never held.
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 51% of all known CVEs.
References
Related Vulnerabilities
Other CWE-835 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-13935 | High | 7.5 | 87% | - | Fix |
| CVE-2014-0050 | High | 7.5 | 83% | - | Fix |
| CVE-2020-36227 | High | 7.5 | 77% | - | Fix |
| CVE-2022-0778 | High | 7.5 | 73% | - | Fix |
| CVE-2024-20353 | High | 8.6 | 71% | KEV | - |
| CVE-2019-14241 | High | 7.5 | 70% | - | - |
Common questions
How do I fix CVE-2026-87082?
No published fix for CVE-2026-87082 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-87082 being actively exploited?
Not that we know of. CVE-2026-87082 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.68% is the estimated probability that it will be exploited in the next 30 days. That is higher than 51% of all scored CVEs.
How severe is CVE-2026-87082?
CVE-2026-87082 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-87082
Markdown
[](https://tridentstack.com/cve/CVE-2026-87082)HTML
<a href="https://tridentstack.com/cve/CVE-2026-87082"><img src="https://tridentstack.com/cve/badge/CVE-2026-87082.svg" alt="CVE-2026-87082"></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.