CVE-2026-3613

Wavlink Wl-nu516u1 Firmware buffer overflow

7.2 HIGHPublic exploitEPSS 1.17%

Published6 Mar 2026

Description

A vulnerability was identified in Wavlink WL-NU516U1 V240425. This vulnerability affects the function sub_401A0C of the file /cgi-bin/login.cgi. Such manipulation of the argument ipaddr leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredHigh

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

Wavlink Wl-nu516u1 Firmwarem16u1_v240425

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/Wlz1112/WAVLINK-NU516-V240425/blob/main/ipaddr_Stack%20Buffer%20Overflow.mdExploitThird Party Advisory
https://vuldb.com/?ctiid.349221Permissions RequiredVDB Entry
https://vuldb.com/?id.349221Third Party AdvisoryVDB Entry
https://vuldb.com/?submit.755341Third Party AdvisoryVDB Entry

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-3613 being actively exploited?

CVE-2026-3613 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.17%.

How severe is CVE-2026-3613?

CVE-2026-3613 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 1.17% probability of exploitation.

Which products are affected by CVE-2026-3613?

Affected products include Wavlink Wl-nu516u1 Firmware.

How do I fix CVE-2026-3613?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-3613 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.