Quick answers
- Is CVE-2026-121944 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121944 being exploited in the wild.
- How severe is CVE-2026-121944?
- Medium severity, with a CVSS score of 5.5, published 4 November 2026.
- Which products and versions are affected?
- Irontec Sngrep through 1.9.0.
- Is there a fix for CVE-2026-121944?
- No fixed version is recorded yet. Avoid processing untrusted pcap files with NFLOG link type, or restrict sngrep to live capture from trusted interfaces only; apply input validation to reject NFLOG packets with malformed TLV structures.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-121944 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121944?
- Check whether you run Irontec Sngrep at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Avoid processing untrusted pcap files with NFLOG link type, or restrict sngrep to live capture from trusted interfaces only; apply input validation to reject NFLOG packets with malformed TLV structures.</anigation> </invoke>
Technical details
An infinite loop exists in capture_packet_reasm_ip() when processing NFLOG TLV (Type-Length-Value) structures; if a non-payload TLV has a length below 4 bytes, the cursor variable link_hl does not advance and the loop condition remains true indefinitely. The vulnerability is triggered when a pcap file specifies NFLOG as the link type (DLT_NFLOG, value 239) and contains a crafted TLV with insufficient length, causing the capture thread to spin without exiting.
Affected products
- Irontec sngrep through 1.9.0
Timeline
- 2026-11-04: disclosed
- 2026-10-21: other: vulnerability reported on GitHub issue #589