CVE-2026-87082
Last modified
CVE-2026-87082 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| — | — | < 2.590 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-87082?
How severe is CVE-2026-87082?
How do I fix CVE-2026-87082?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-87076Tanium addressed an information disclosure vulnerability in …6.5
- CVE-2026-87078Net::IDN::Punycode versions from 2.302 before 2.590 for Perl…9.1
- CVE-2026-87079Net::IDN::Punycode versions before 2.590 for Perl allow CPU …7.5
- CVE-2026-8708The Genzel breadcrumbs plugin for WordPress is vulnerable to…4.3
- CVE-2026-87080Net::IDN::Punycode::PP versions before 2.590 for Perl decode…9.1
- CVE-2026-87081Net::IDN::UTS46 versions before 2.590 for Perl allow CPU exh…7.5
- CVE-2026-87083A weakness has been identified in tile-ai tilelang up to 0.1…5.5
- CVE-2026-87084Tanium addressed a server-side request forgery vulnerability…7.7
- CVE-2026-87087Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-87088Tanium addressed an unauthorized code execution vulnerabilit…7
- CVE-2026-8709An improper privilege management vulnerability in the REST A…9.9
- CVE-2026-87090Consul and Consul Enterprise are vulnerable to an authorizat…8.3
Are you affected by CVE-2026-87082?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
