CVE & CISA-KEV Catalog

CVE-2026-87079

HIGH
7.5
CVSS v3
NVD

Description

Net::IDN::Punycode versions before 2.590 for Perl allow CPU exhaustion via quadratic insertion cost when decoding a long label in decode_punycode. The XS backend inserts each decoded code point into a UTF-8 buffer and finds the insertion point by scanning that buffer from the start, one character at a time. The scan runs once per code point over the output built so far, so the cost is quadratic in the label length. The pure-Perl backend downgrades its input to bytes so that substr can index it directly, but takes its working copy before the downgrade, so when the input carries the UTF-8 flag every substr on the copy scans from the start, with the same quadratic cost. Nothing bounds the label length in the to-Unicode direction. The 63-byte DNS limit is checked only when converting to ASCII, so domain_to_unicode and uts46_to_unicode pass an attacker-supplied label of any length to the decoder.

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

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.63%probability of exploitation in 30 days
49thpercentile

Moderate risk: more likely to be exploited than 49% of all known CVEs.

References

Related Vulnerabilities

Other CWE-407 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2020-27223Medium5.278%-Fix
CVE-2022-36021Medium5.560%-Fix
CVE-2021-33582High7.53.1%-Fix
CVE-2024-43485High7.53.1%-Fix
CVE-2024-43484High7.53.0%-Fix
CVE-2016-10396High7.52.9%--

Common questions

How do I fix CVE-2026-87079?

No published fix for CVE-2026-87079 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-87079 being actively exploited?

Not that we know of. CVE-2026-87079 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.63% is the estimated probability that it will be exploited in the next 30 days. That is higher than 49% of all scored CVEs.

How severe is CVE-2026-87079?

CVE-2026-87079 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-87079
CVE-2026-87079 severity badge

Markdown

[![CVE-2026-87079](https://tridentstack.com/cve/badge/CVE-2026-87079.svg)](https://tridentstack.com/cve/CVE-2026-87079)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-87079"><img src="https://tridentstack.com/cve/badge/CVE-2026-87079.svg" alt="CVE-2026-87079"></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.

Run a free CVE scan on your fleetStart freeThis CVE lookup is free and always will be.

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.