Quick answers
- Is CVE-2026-74766 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74766 being exploited in the wild.
- How severe is CVE-2026-74766?
- High severity, with a CVSS score of 8.4, published 22 September 2026.
- Which products and versions are affected?
- CPAN Net::IDN::Punycode 2.301 through 2.589.
- Is there a fix for CVE-2026-74766?
- A patch was published on 2026-08-17: Fix committed upstream in Net-IDN-Encode repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74766 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-74766?
- Check whether you run CPAN Net::IDN::Punycode at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The XS backend's decode_punycode function computes an insertion pointer into the output buffer before growing the buffer to accommodate new bytes. When the buffer is reallocated during growth, all internal pointers are updated except the insertion pointer, which remains stale. Subsequent memory operations use the freed pointer. The vulnerability is triggered when decoding code points above U+FFFF (which require 4 bytes in UTF-8) in labels long enough to force buffer reallocation. The fix moves the buffer growth before pointer calculation.
Affected products
- CPAN Net::IDN::Punycode 2.301 through 2.589
Timeline
- 2026-09-22: disclosed
- 2026-08-17: patched: Fix committed upstream in Net-IDN-Encode repository