CVE-2026-5265 is a heap over-read vulnerability in multiple versions of OVN (Open Virtual Network) affecting ovn-controller, specifically the userspace pinctrl thread when generating ICMP Destination Unreachable or ICMP Packet Too Big responses. The vulnerable logic copies part of the original packet into the ICMP error payload using attacker-controlled IP length fields—IPv4 ip_tot_len or IPv6 ip6_plen—without validating those declared lengths against the actual packet buffer size. A malicious VM can send a truncated or short packet with an inflated IP length field that is processed along a path that generates an ICMP error, such as reject ACL handling, Gateway MTU checks on logical router ports, or reject-configured load balancers with no backends. This causes ovn-controller to read beyond the valid packet data from heap memory and embed the over-read bytes into the ICMP response returned to the originating workload.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.