# CVE-2018-25268: LanSpy 2.0.1.159 Local Buffer Overflow via Scan Field

> Attackers can trigger a buffer overflow in LanSpy via oversized scan field input, potentially leading to arbitrary code execution or application crashes.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-m76w-v74r-fqv2

## What is CVE-2018-25268?

CVE-2018-25268 is a high-severity memory corruption vulnerability in Lizardsystems LanSpy, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

LanSpy 2.0.1.159 contains a local buffer overflow vulnerability that allows attackers to overwrite the instruction pointer by supplying oversized input to the scan field. Attackers can craft a payload with 688 bytes of padding followed by 4 bytes of controlled data to crash the application or potentially achieve code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-25268?

It affects 1 product.


Products: Lizardsystems Lanspy.

## How do I fix CVE-2018-25268?

No fix has been published for CVE-2018-25268 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25268 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25268 exists.

## Other vulnerabilities in Lizardsystems LanSpy

- [CVE-2018-25265](https://insights.sbomify.com/CVE-2018-25265/): LanSpy 2.0.1.159 Local Buffer Overflow (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25268 and fix it if it is affected.

What it is: CVE-2018-25268 is a high-severity memory corruption vulnerability in Lizardsystems LanSpy, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25268 exists.

Affected product: Lizardsystems LanSpy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25268/ (Markdown: https://insights.sbomify.com/CVE-2018-25268/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25268
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25268
- OSV: https://osv.dev/vulnerability/CVE-2018-25268

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25268/
Summaries are generated and may contain mistakes; the official description above is the record.