# CVE-2026-57877: GV-LPC2011/LPC2211 - unauthorized format string vulnerability (vlsvr)

> Remote attackers can exploit a format string vulnerability in GeoVision cameras to cause information disclosure, memory corruption, or denial of service.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-3ff2-4v74-vhq8

## What is CVE-2026-57877?

CVE-2026-57877 is a high-severity vulnerability in GeoVision Inc. GV-LPCLPC2011/2211, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated
format string vulnerability exists in vlsvr in GeoVision GV-LPC2011 and
GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper handling
of externally controlled input during log message formatting in the login
processing path. A remote attacker may exploit this vulnerability by sending
crafted login data, potentially causing information disclosure, memory
corruption, or a denial of service.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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


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

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

## Is CVE-2026-57877 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57877 is a high-severity vulnerability in GeoVision Inc. GV-LPCLPC2011/2211, published on 26 Jun 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-57877 in the wild and no public exploit code.

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

## Sources

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

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