# CVE-2026-108984: GV-ASManager Web Server Buffer Overflow Vulnerability

> A buffer overflow in the GeoVision GV-ASManager web server allows attackers to execute arbitrary code or cause denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-ff97-3788-cg27

## What is CVE-2026-108984?

CVE-2026-108984 is a high-severity memory corruption vulnerability in GeoVision Inc. GV-ASManager, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability is in Web Server default connection ports under the process name GeoWebServer.exe .

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-108984?


## How do I fix CVE-2026-108984?

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

## Is CVE-2026-108984 being exploited?

There is no known exploitation of CVE-2026-108984 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108984 and fix it if it is affected.

What it is: CVE-2026-108984 is a high-severity memory corruption vulnerability in GeoVision Inc. GV-ASManager, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108984 in the wild and no public exploit code.

Affected product: GeoVision Inc. GV-ASManager. 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-2026-108984/ (Markdown: https://insights.sbomify.com/CVE-2026-108984/index.md)
```

## Sources

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

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