CVE-2026-8836
Stack-Based Buffer Overflow in lwIP SNMPv3 USM Handler
Publication date: 2026-05-18
Last updated on: 2026-05-18
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lwip | lwip | to 2.2.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the lwIP library up to version 2.2.1, specifically in the function snmp_parse_inbound_frame within the snmpv3 USM Handler component. It occurs when the argument msgAuthenticationParameters is manipulated, leading to a stack-based buffer overflow. This means that an attacker can send specially crafted data to overflow the buffer on the stack, potentially causing unexpected behavior or allowing code execution.
The attack can be initiated remotely, meaning an attacker does not need local access to exploit this vulnerability.
A patch has been released to fix this issue, identified by the commit 0c957ec03054eb6c8205e9c9d1d05d90ada3898c.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code, cause a denial of service, or crash the affected system.
Since the attack can be performed remotely without any privileges or user interaction, it poses a high risk to systems using vulnerable versions of lwIP.
The CVSS scores indicate a critical severity level, with a maximum score of 10.0 in version 2.0 and very high scores in later versions, reflecting the potential for significant impact on confidentiality, integrity, and availability.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to install the patch named 0c957ec03054eb6c8205e9c9d1d05d90ada3898c that addresses the issue in the snmp_parse_inbound_frame function of lwIP.