CVE-2026-56015: Net::IP::LPM versions before 1.11 for Perl allow a heap out-of-bounds read via an unbounded prefix length
Net::IP::LPM versions before 1.11 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.
Security readout for executives and security teams
Plain-English summary
A malformed IP prefix supplied to Perl's Net::IP::LPM before version 1.11 can make the module read beyond a small memory buffer while building its lookup trie. Hardened environments may terminate the process, creating a denial-of-service risk. The supplied description says those extra bytes are not returned through the module API.
Executive priority
Prioritize rapid remediation for externally reachable services that pass user-controlled prefixes into this module, especially where process termination affects availability. Other deployments should patch through normal expedited dependency maintenance after confirming reachability. Treat the critical score seriously, but validate context because the supplied technical description supports denial of service more clearly than data disclosure.
Technical view
The add() method accepts prefix lengths exceeding IPv4's 32-bit or IPv6's 128-bit width. addPrefixToTrie() then reads beyond the packed 4-byte or 16-byte address buffer. The length is an unsigned byte, bounding the walk to 32 bytes from the buffer start. The issue occurs during trie construction and may trigger allocator, AddressSanitizer, or valgrind failures.
Likely exposure
Exposure requires Net::IP::LPM earlier than 1.11 and a path allowing an attacker to influence prefix strings passed to add(). Internet reachability depends on the surrounding application, not the module alone. Systems using only trusted, validated prefixes have lower practical exposure. The bundle's affected-package metadata is internally inconsistent, so confirm deployed versions directly.
Exploitation context
The bundle does not report active exploitation, and the CVE is not listed as KEV. The documented consequence is a bounded out-of-bounds read that can abort a process under hardened memory handling. Although the supplied CVSS assigns high confidentiality impact, the description states out-of-bounds bytes are not exposed through lookups or dump().
Researcher notes
CWE-125 fits the documented heap out-of-bounds read. The source bundle identifies versions before 1.11 as vulnerable and supplies both a 1.10 patch and 1.11 release notes. Its structured affected entry also lists version "0" with default status "unaffected," conflicting with the narrative. The CVSS confidentiality rating likewise conflicts with the statement that API output does not expose adjacent bytes.
Mitigation direction
Upgrade Net::IP::LPM to version 1.11 or later.
If upgrading is delayed, evaluate the cited MetaCPAN patch for version 1.10.
Reject IPv4 prefix lengths above 32 and IPv6 lengths above 128 before calling add().
Review CPAN guidance for any later remediation or compatibility information.
Validation and detection
Inventory applications and dependency locks for Net::IP::LPM versions earlier than 1.11.
Trace whether untrusted input can reach the module's add() method.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.