CVE-2026-48690
published 2026-05-26CVE-2026-48690: FastNetMon Community Edition through 1.2.9 contains an integer overflow vulnerability in the packet capture buffer allocation. In src/packet_storage.hpp, the…
PriorityP337high7.1CVSS 3.1
AVLACLPRLUINSUCHIHAN
EPSS
0.12%
1.9th percentile
FastNetMon Community Edition through 1.2.9 contains an integer overflow vulnerability in the packet capture buffer allocation. In src/packet_storage.hpp, the allocate_buffer() function computes memory_size_in_bytes as 'buffer_size_in_packets * (max_captured_packet_size + sizeof(fastnetmon_pcap_pkthdr_t)) + sizeof(fastnetmon_pcap_file_header_t)' using unsigned int (32-bit) arithmetic. With max_captured_packet_size=1500 and sizeof(fastnetmon_pcap_pkthdr_t)=16, each packet requires approximately 1516 bytes. If buffer_size_in_packets exceeds approximately 2,832,542, the multiplication overflows, resulting in a much smaller allocation than expected. Subsequent write_packet() calls then write past the allocated buffer, causing heap corruption. The buffer_size_in_packets value is derived from the ban_details_records_count configuration parameter, which is parsed using atoi() with no overflow checking.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| pavel-odintsov | fastnetmon | <= 1.2.9 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [epel-all]
bugzilla·2026-05-28·CVSS 7.1
CVE-2026-48690 [HIGH] CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [epel-all]
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [fedora-all]
bugzilla·2026-05-28·CVSS 7.1
CVE-2026-48690 [HIGH] CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [fedora-all]
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation
bugzilla·2026-05-26·CVSS 7.1
CVE-2026-48690 [HIGH] CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation
CVE-2026-48690 fastnetmon: integer overflow in the packet capture buffer allocation
FastNetMon Community Edition through 1.2.9 contains an integer overflow vulnerability in the packet capture buffer allocation. In src/packet_storage.hpp, the allocate_buffer() function computes memory_size_in_bytes as 'buffer_size_in_packets * (max_captured_packet_size + sizeof(fastnetmon_pcap_pkthdr_t)) + sizeof(fastnetmon_pcap_file_header_t)' using unsigned int (32-bit) arithmetic. With max_captured_packet_size=1500 and sizeof(fastnetmon_pcap_pkthdr_t)=16, each packet requires approximately 1516 bytes. If buffer_size_in_packets exceeds approximately 2,832,542, the multiplication overflows, resulting in a much smaller allocation than expected. Subsequent write_packet() calls then write past the allocated
2026-05-26
Published