wireguard-lwip denial of service in session index allocator
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
A flaw in the smartalock wireguard-lwip software lets an attacker with local access and high privileges manipulate the receiver_index argument in its Session Index Allocator, causing unintended resource allocation. The project was told about the problem early through an issue report but has not yet responded.
Written by a model
Original description
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 to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133413 (smartalock wireguard-lwip Session Index Allocator wireguard.c wireguard_generate_unique_index allocation of resources), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133413 (entry last updated 2026-11-20):
Affected:
- smartalock wireguard-lwip: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133413 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133413 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/smartalock/wireguard-lwip/issues/22
- https://vuldb.com/vuln/440647
- https://vuldb.com/vuln/440647/cti
- https://vuldb.com/cve/CVE-2026-133413
- https://vuldb.com/submit/1048145
- https://github.com/smartalock/wireguard-lwip/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133413
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133413"}.Affected versions
- smartalock wireguard-lwipVersion range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.6/10CVSS 4.6
- No patch5/5No patch listed yet
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133413 |
| Record | NVD · CVE-2026-133413 |
| Other links 6 | |
| Advisory | VulDB · Advisory #440647 |
| Advisory | VulDB · Threat intelligence #440647 |
| Advisory | VulDB · CVE-2026-133413 record |
| Advisory | VulDB · Submission #1048145 |
| Report | GitHub · smartalock/wireguard-lwip · Issue #22 |
| Repository | GitHub · smartalock/wireguard-lwip · Repository |
Related
- CVE-2026-133201smartalock wireguard-lwip X25519 Ladder x25519.c mul out-of-bounds write
- CVE-2026-61827netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- CVE-2026-127960Denial of service through folded HTTP response headers
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
- CVE-2026-63124netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
No corrections so far. Something wrong on this page? Report an error.