cve.bz

CVE-2026-87080

9.1 criticalEPSS 0.4%

Critical (9.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Net::IDN::Punycode::PP versions before 2.590 for Perl decode a truncated label to a name containing a character it never encoded in decode_punycode. The pure-Perl decoder reads one digit at a time with four-argument substr and tests the result with defined to detect the end of the input. substr on an exhausted string returns the empty string rather than undef, so decoding continues past the end. The empty string converts to a digit value below the range, reducing the accumulator, and the decoder derives one extra code point and its position from it. The result is deterministic. The XS backend rejects the same label. Net::IDN::Punycode uses this backend wherever the XS does not build. The two backends disagree about what such a label means, so a sender can pick a label that one installation resolves to a name and another rejects.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-09-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1286 Improper Validation of Syntactic Correctness of Input
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-87080 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-87080?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-87080?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-87080 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libnet-idn-encode-perlno fix listedDEBIAN-CVE-2026-87080
Debian14libnet-idn-encode-perl2.600-1DEBIAN-CVE-2026-87080
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibnet-idn-encode-perlno fix listedUBUNTU-CVE-2026-87080
openSUSETumbleweedperl-Net-IDN-Encode2.600.0-1.1openSUSE-SU-2026:12468-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-676 NoSQL Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON