CVE-2026-133413smartalock wireguard-lwip uncontrolled resource consumption
CVE-2026-133413 is a uncontrolled resource consumption in smartalock wireguard-lwip, rated medium (4.6 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
Requests can consume unbounded CPU, memory or connections and starve the service. Resources are allocated without a cap, so a caller can exhaust them.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an administrator account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker exhaust CPU, memory or connections until the service stops answering.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place smartalock wireguard-lwip runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
A vulnerability was detected in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. This affects the function wireguard_generate_unique_index of the file src/wireguard.c of the component Session Index Allocator. The manipulation of the argument receiver_index results in allocation of resources. The attack is only possible with local access. The project was informed of the problem early through an issue report but has not responded yet.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.
Questions to answer about your own systems
- Where does smartalock wireguard-lwip run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.