smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a X25519 Ladder src/crypto/refc/x25519.c mul out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.23+ |
Summary
A vulnerability was found in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. It has been rated as critical. The affected element is the function mul of the file src/crypto/refc/x25519.c of the component X25519 Ladder. The manipulation leads to out-of-bounds write.
This vulnerability is uniquely identified as CVE-2026-133201. The attack is possible to be carried out remotely. No exploit exists.
This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as critical, has been found in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. This issue affects the function mul of the file src/crypto/refc/x25519.c of the component X25519 Ladder. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-133201. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/19/2026).
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.5
VulDB Temp Score: 7.5
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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: 21
Status: Confirmed
CNA: VulDB
CVE: CVE-2026-133201 (🔒)
GCVE (CVE): GCVE-0-2026-133201
GCVE (VulDB): GCVE-100-440237
Entry
Created: 11/19/2026 16:02Changes: 11/19/2026 16:02 (56)
Complete: 🔍
Submitter: Timmmy
Cache ID: 216::103
Submit
Accepted
- Submit #1045504: smartalock wireguard-lwip `6e65ae6f (verified); c54f20db (main, presumed affected)` Memory Corruption (by Timmmy)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.