CVE-2026-56015: CWE-125 Out-of-bounds Read in TPODER Net::IP::LPM
Net::IP::LPM versions through 1.10 for Perl allow a heap out-of-bounds read via an unbounded prefix length. add() passes the prefix string to the trie builder addPrefixToTrie() without checking it against the address width. addPrefixToTrie() then walks the prefix buffer by prefix_length bits, reading prefix[byte] for byte up to prefix_len/8, where prefix is the 4-byte (IPv4) or 16-byte (IPv6) packed address. A prefix length greater than 32 for IPv4 or 128 for IPv6, for example add("1.2.3.4/255", $v) or add("2001:db8::/255", $v), reads past the end of the packed address. The out-of-bounds read happens during trie construction and is bounded: the prefix length is stored as an unsigned char, so the bit walk reads at most 32 bytes from the start of the packed address, a short distance past the end of the 4-byte or 16-byte buffer. It is detectable under AddressSanitizer, valgrind, or a hardened allocator, where it can abort the process. Lookups and dump() format only the valid address width, so the out-of-bounds bytes are not exposed through the module's API.
AI Analysis
Technical Summary
CVE-2026-56015 is a heap out-of-bounds read vulnerability in Net::IP::LPM versions up to 1.10 for Perl. The add() function passes a prefix string to addPrefixToTrie() without validating the prefix length against the address width (32 bits for IPv4, 128 bits for IPv6). If the prefix length exceeds these bounds (e.g., /255), addPrefixToTrie() reads beyond the allocated packed address buffer by up to 32 bytes due to the prefix length being stored as an unsigned char. This out-of-bounds read occurs during trie construction and can be detected by memory safety tools, potentially causing process termination. The vulnerability does not leak out-of-bounds data through the module's API during lookups or dumps.
Potential Impact
The vulnerability allows a heap out-of-bounds read which can lead to process crashes or aborts when memory safety tools or hardened allocators are used. It does not directly expose sensitive data through the module's API. The CVSS score of 9.1 indicates a critical severity with high confidentiality impact and high availability impact, but no integrity impact. There are no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing prefix lengths exceeding the valid address width (greater than 32 for IPv4 or 128 for IPv6) to the add() function. Use memory safety tools to detect potential exploitation attempts. Monitor vendor channels for official patches or updates.
CVE-2026-56015: CWE-125 Out-of-bounds Read in TPODER Net::IP::LPM
Description
Net::IP::LPM versions through 1.10 for Perl allow a heap out-of-bounds read via an unbounded prefix length. add() passes the prefix string to the trie builder addPrefixToTrie() without checking it against the address width. addPrefixToTrie() then walks the prefix buffer by prefix_length bits, reading prefix[byte] for byte up to prefix_len/8, where prefix is the 4-byte (IPv4) or 16-byte (IPv6) packed address. A prefix length greater than 32 for IPv4 or 128 for IPv6, for example add("1.2.3.4/255", $v) or add("2001:db8::/255", $v), reads past the end of the packed address. The out-of-bounds read happens during trie construction and is bounded: the prefix length is stored as an unsigned char, so the bit walk reads at most 32 bytes from the start of the packed address, a short distance past the end of the 4-byte or 16-byte buffer. It is detectable under AddressSanitizer, valgrind, or a hardened allocator, where it can abort the process. Lookups and dump() format only the valid address width, so the out-of-bounds bytes are not exposed through the module's API.
CVSS v3.1
Score 9.1critical
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-56015 is a heap out-of-bounds read vulnerability in Net::IP::LPM versions up to 1.10 for Perl. The add() function passes a prefix string to addPrefixToTrie() without validating the prefix length against the address width (32 bits for IPv4, 128 bits for IPv6). If the prefix length exceeds these bounds (e.g., /255), addPrefixToTrie() reads beyond the allocated packed address buffer by up to 32 bytes due to the prefix length being stored as an unsigned char. This out-of-bounds read occurs during trie construction and can be detected by memory safety tools, potentially causing process termination. The vulnerability does not leak out-of-bounds data through the module's API during lookups or dumps.
Potential Impact
The vulnerability allows a heap out-of-bounds read which can lead to process crashes or aborts when memory safety tools or hardened allocators are used. It does not directly expose sensitive data through the module's API. The CVSS score of 9.1 indicates a critical severity with high confidentiality impact and high availability impact, but no integrity impact. There are no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing prefix lengths exceeding the valid address width (greater than 32 for IPv4 or 128 for IPv6) to the add() function. Use memory safety tools to detect potential exploitation attempts. Monitor vendor channels for official patches or updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-06-18T11:27:09.117Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a47b76327e9c79719be3e71
Added to database: 07/03/2026, 13:21:39 UTC
Last enriched: 07/11/2026, 08:56:17 UTC
Last updated: 08/15/2026, 12:41:10 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.