FASTNETMON · CVE-2026-92695 · Package
NO FIX YET · SEE WHAT TO DO
FastNetMon, a DDoS detection sensor, reads past the end of captured packet data when pcap capture is enabled, because the parser does not check the captured length. A remote sender of a short or malformed IPv4 frame can make the process crash.
first public Jul 20, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only deployments that run FastNetMon's live pcap capture (pcap = on) are exposed, because the flawed callback in pcap_collector.cpp handles captured frames only in that mode. Teams running FastNetMon on a mirror or sensor port that receives attacker-influenced traffic should look first. Deployments with pcap capture off, or not running FastNetMon, can skip it.
Not affected if not-fastnetmon, pcap-off
Who cares ddos-detection, fastnetmon, network-sensor, pcap
FastNetMon is a high-performance DDoS detector and sensor. In version 1.2.9 and earlier, the live parse_packet() callback in src/pcap_plugin/pcap_collector.cpp is registered through pcap_loop and processes captured frames when pcap = on without checking packethdr->caplen. A short frame or an attacker-controlled IPv4 header length can make the parser dereference IP or transport headers beyond the captured bytes, causing an out-of-bounds read and process termination. No fixed release is available as of this review.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
1.2.9)