CVE-2026-133201 json
smartalock wireguard-lwip X25519 Ladder x25519.c mul out-of-bounds write
published 5h ago modified 4h ago also EUVD-2026-130721
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
A vulnerability was determined in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. Impacted is the function mul of the file src/crypto/refc/x25519.c of the component X25519 Ladder. Executing a manipulation can lead to out-of-bounds write. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Is CVE-2026-133201 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:X/RL:X/RC:C |
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:X/RL:X/RC:C |
| CNA | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C/E:ND/RL:ND/RC:C |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- smartalock wireguard-lwip
Classification
References
-
vuldb.com
/vuln/440237
vdb-entry, technical-description
-
vuldb.com
/vuln/440237/cti
signature, permissions-required
-
vuldb.com
/cve/CVE-2026-133201
third-party-advisory
-
vuldb.com
/submit/1045504
third-party-advisory
-
github.com
/smartalock/wireguard-lwip/issues/21
issue-tracking
-
github.com
/smartalock/wireguard-lwip/
product
Sources
- CVE List CVE-2026-133201
- NVD CVE-2026-133201
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.