# CVE-2026-57874: GV-LPC2011/LPC2211 - unauthorized buffer overflow vulnerability (IEEE8021x_upload.cgi)

> A remote unauthenticated attacker can cause a denial of service via a buffer overflow in the IEEE8021x upload CGI script.

- **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:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-vrjw-2c7c-hhv6

## What is CVE-2026-57874?

CVE-2026-57874 is a high-severity memory corruption 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
buffer overflow vulnerability exists in IEEE8021x_upload.cgi in GeoVision
GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by
insufficient bounds checking when parsing filename values in multipart upload
data. A remote attacker may exploit this vulnerability by sending a crafted
upload request with overly long input, causing memory corruption and resulting
in a denial of service.

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

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


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

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

## Is CVE-2026-57874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57874 is a high-severity memory corruption 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-57874 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-57874/ (Markdown: https://insights.sbomify.com/CVE-2026-57874/index.md)
```

## Sources

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

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