CVE-2026-74766
8.4Perl · Net::IDN::Punycode
A heap use-after-free vulnerability in the Perl Net::IDN::Punycode XS backend allows attackers to corrupt memory during the decoding of punycode labels.
Executive summary
A heap use-after-free vulnerability in the Perl Net::IDN::Punycode module allows for potential memory corruption, posing a high risk to applications utilizing the affected XS backend.
Vulnerability
This is a use-after-free vulnerability (CWE-416) triggered when the XS backend reallocates an output buffer during punycode decoding, leaving a dangling pointer that is subsequently written to. The vulnerability does not require authentication to trigger, as it is processed during the decoding of attacker-supplied input.
Business impact
The vulnerability carries a CVSS score of 8.4, reflecting its potential for severe impact including arbitrary code execution, system crashes, or data corruption. Because the flaw involves low-level memory management errors, it could allow an attacker to bypass security controls or gain unauthorized access to the underlying system memory, posing a significant risk to data integrity and service availability.
Remediation
Immediate Action: Upgrade the Net::IDN::Punycode module to version 2.590-TRIAL or later to resolve the memory allocation defect.
Proactive Monitoring: Monitor application logs for unusual segmentation faults or unexpected process terminations that may indicate exploitation attempts against the punycode decoding routine.
Compensating Controls: If immediate patching is not feasible, restrict the processing of untrusted punycode input or implement input validation to reject malformed labels that trigger the vulnerable memory reallocation path.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Given the severity of memory corruption vulnerabilities, organizations should prioritize updating the Net::IDN::Punycode module to the fixed version. The potential for arbitrary code execution necessitates a rapid response to ensure that applications handling user-supplied punycode strings are no longer susceptible to this memory safety issue.
More Perl CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 8.4 (3.1) from cvelistV5
- Analyst report written
- Published in the daily brief high section