Quick answers
- Is CVE-2026-52195 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52195 being exploited in the wild.
- How severe is CVE-2026-52195?
- Informational severity, with a CVSS score of 7.5, published 30 June 2026.
- Which products and versions are affected?
- UTT NV518G v3.2.7-210919-161313; UTT nv518GV3 v3.2.7-210919-161313.
- Is there a fix for CVE-2026-52195?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. 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-52195 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52195?
- Check whether you run UTT NV518G or UTT nv518GV3 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.
Technical details
A stack-based buffer overflow exists in the 'gohead/sub_472f08' component of UTT nv518G routers. The vulnerability is located in the handling of the 'delstr' POST parameter, which is processed using strtok_r() and sscanf() to extract MAC addresses. The function uses strncpy() to write data into a 1500-byte stack buffer (v24) within a loop. While there is a loop bound check (n4 < 1462), it is insufficient because each iteration advances the write pointer by 38 bytes. After approximately 40 iterations, the writes exceed the buffer's bounds, overwriting adjacent stack variables and the return address, leading to a crash or potential remote code execution.
Affected products
- UTT nv518G nv518GV3 v3.2.7-210919-161313
Timeline
- 2026-06-30: disclosed: Initial disclosure via GitHub and CVE assignment