smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a Session Index Allocator src/wireguard.c wireguard_generate_unique_index receiver_index allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.47+ |
Summary
A vulnerability marked as problematic has been reported in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. This impacts the function wireguard_generate_unique_index of the file src/wireguard.c of the component Session Index Allocator. This manipulation of the argument receiver_index causes allocation of resources.
This vulnerability is tracked as CVE-2026-133413. The attack is restricted to local execution. No exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. It has been declared as problematic. Affected by this vulnerability is 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 with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. As an impact it is known to affect integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-133413. The exploitation appears to be easy. Attacking locally is a requirement. Additional levels of successful authentication are required for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.4VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.4
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/19/2026 Advisory disclosed11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 22
Status: Confirmed
CNA: VulDB
CVE: CVE-2026-133413 (🔒)
GCVE (CVE): GCVE-0-2026-133413
GCVE (VulDB): GCVE-100-440647
Entry
Created: 11/19/2026 19:59Changes: 11/19/2026 19:59 (56)
Complete: 🔍
Submitter: Timmmy
Cache ID: 216::103
Submit
Accepted
- Submit #1048145: smartalock wireguard-lwip 6e65ae6f (verified); c54f20db (main, affected) Business Logic Errors (by Timmmy)
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.