# CVE-2018-25328: VX Search 10.6.18 Local Buffer Overflow via Directory Field

> Attackers can execute arbitrary code with application privileges by exploiting a local buffer overflow in the directory field of VX Search.

- **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:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-wcf6-c97r-gp58

## What is CVE-2018-25328?

CVE-2018-25328 is a high-severity memory corruption vulnerability in vxsearch VX Search, published on 17 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VX Search 10.6.18 contains a local buffer overflow vulnerability that allows attackers to overwrite the instruction pointer by supplying an oversized string in the directory field. Attackers can craft a malicious input file containing 271 bytes of junk data followed by a return address to execute arbitrary code with application privileges.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2018-25328 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25328 is a high-severity memory corruption vulnerability in vxsearch VX Search, published on 17 May 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-25328 exists.

Affected product: vxsearch VX Search. 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-25328/ (Markdown: https://insights.sbomify.com/CVE-2018-25328/index.md)
```

## Sources

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

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