CVE-2026-87081 Affecting libnet-idn-encode-perl package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN12-LIBNETIDNENCODEPERL-20044826
  • published22 Sept 2026
  • disclosed22 Sept 2026

Introduced: 22 Sep 2026

NewCVE-2026-87081  (opens in a new tab)

How to fix?

There is no fixed version for Debian:12 libnet-idn-encode-perl.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libnet-idn-encode-perl package and not the libnet-idn-encode-perl package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

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.