FastNetMon Community Edition through 1.2.9 contains an off-by-one heap-based buffer overflow in the dynamicbinarybuffert class (src/dynamicbinarybuffer.hpp). Five methods (appenddynamicbuffer, appenddataaspointer, appenddataasobjectptr, memcpyfromptr, memcpyfromobjectptr) use an incorrect bounds check of the form 'if (offset + length > maximuminternalstoragesize + 1)' instead of the correct 'if (offset + length > maximuminternalstoragesize)'. This allows writing exactly one byte past the end of the heap-allocated buffer. The class is used pervasively in BGP message encoding/decoding, NetFlow template processing, and Flow Spec NLRI construction. An attacker who can send network traffic (NetFlow, sFlow, IPFIX, or BGP) to a FastNetMon instance can trigger this overflow, potentially achieving arbitrary code execution by corrupting heap metadata. Notably, the appendbyte() method uses the correct bounds check, confirming the inconsistency.
{
"cna_assigner": "mitre",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48689.json"
}{
"extracted_events": [
{
"introduced": "0"
},
{
"fixed": "1.2.9"
},
{
"introduced": "0"
},
{
"last_affected": "1.2.9"
}
],
"source": [
"DESCRIPTION",
"CPE_RANGE"
],
"cpe": "cpe:2.3:a:pavel-odintsov:fastnetmon:*:*:*:*:community:*:*:*"
}