Heap memory corruption via stale insertion pointer
Published Sep 22, 2026 · Updated Sep 22, 2026
Heap use-after-free in Net::IDN::Punycode 2.301 through 2.589 allows attackers to corrupt memory via a crafted Punycode label. decode_punycode calculates an insertion pointer before enlarging its scalar output buffer, then retains that stale pointer after reallocation and uses it to move data and write the decoded code point. Only programs using the XS backend to decode attacker-supplied labels expose the freed-memory read and write.
Summary
What happened
Heap use-after-free in Net::IDN::Punycode 2.301 through 2.589 allows attackers to corrupt memory via a crafted Punycode label. decode_punycode calculates an insertion pointer before enlarging its scalar output buffer, then retains that stale pointer after reallocation and uses it to move data and write the decoded code point. Only programs using the XS backend to decode attacker-supplied labels expose the freed-memory read and write.
The record
- CVE
- CVE-2026-74766
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- Paul Johnson
- Product
- Net::IDN::Punycode
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.301 <2.590
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started