# CVE-2026-12488: GeoVision GV-VMS V20 GV-Cloud memory corruption vulnerability

> A memory corruption flaw in GeoVision GV-VMS allows attackers to cause denial of service by impersonating the legitimate server.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-7j74-f2vx-3rfg

## What is CVE-2026-12488?

CVE-2026-12488 is a medium-severity memory corruption vulnerability in GeoVision, published on 24 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A memory corruption vulnerability exists in the GV-Cloud functionality of GeoVision GV-VMS V20 20.0.2. 

A specially crafted network request can lead to a denial of service. An attacker can impersonate the legitimate server to trigger this vulnerability.

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

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


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

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

## Is CVE-2026-12488 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12488 is a medium-severity memory corruption vulnerability in GeoVision, published on 24 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-12488 in the wild and no public exploit code.

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

## Sources

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

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