CVE-2026-2259
Memory Corruption in aardappel lobster Parser via Local Exploit
Publication date: 2026-02-10
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| strlen | lobster | to 2025.4 (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-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the aardappel lobster software up to version 2025.4, specifically in the function lobster::Parser::ParseStatements within the parsing component. It allows an attacker with local access to manipulate the function in a way that causes memory corruption.
The vulnerability can only be exploited from a local environment, meaning remote exploitation is not possible. A patch has been released to fix this issue.
How can this vulnerability impact me? :
The vulnerability leads to memory corruption, which can potentially cause the affected software to behave unpredictably or crash.
Since the attack requires local access, an attacker would need to have some level of access to the system already. The impact is rated as low to moderate based on CVSS scores, with no confidentiality or integrity loss, but possible availability impact.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate step to mitigate this vulnerability is to apply the patch identified by commit 2f45fe860d00990e79e13250251c1dde633f1f89.
Since the attack can only be performed from a local environment, limiting local access to trusted users can also help reduce risk.