CVE-2026-87080: Net-IDN-Encode (Perl module) · Improper Validation of Syntactic Correctness of Input
Affects Net-IDN-Encode (Perl module)Source CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.590 as a priority.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.590
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Net-IDN-Encode (Perl module) to 2.590.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CPANNet-IDN-Encodepkg:cpan/Net-IDN-EncodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fixed version 2.590 or later of Net::IDN::Punycode::PP addresses this issue. Users should upgrade to version 2.590 or newer to resolve the vulnerability. No vendor advisory or patch link was provided, so check the official Net::IDN::Punycode repository or CPAN for the official patch and upgrade instructions.
Description
CVE-2026-87080 affects Net::IDN::Punycode::PP versions before 2.590 for Perl. The vulnerability arises from improper validation of syntactic correctness when decoding truncated labels, causing the pure-Perl decoder to produce a name containing characters it never encoded. This discrepancy between the pure-Perl and XS backends can lead to inconsistent resolution of domain labels.