CVE-2026-57874
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated buffer overflow exists in the IEEE8021x_upload.cgi script on GeoVision GV-LPC2011 and GV-LPC2211 IP camera firmware V1.12 and earlier. The vulnerability stems from inadequate bounds checking when the CGI parser processes the filename parameter within multipart HTTP upload requests, allowing an attacker to trigger memory corruption via oversized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the physical label or web interface of the IP camera to confirm it is a GeoVision GV-LPC2011 or GV-LPC2211 model.Affected if The device is a GeoVision GV-LPC2011 or GV-LPC2211 IP camera.
-
Check the installed firmware versionAccess the camera's web administration interface and navigate to the system information or firmware upgrade page to view the current firmware version. Alternatively, use the vendor's discovery tool or check the firmware file if an upgrade has been performed.Affected if The firmware version is V1.12 or earlier.
-
Confirm the IEEE8021x_upload.cgi endpoint is reachableAttempt to access the CGI script via HTTP/HTTPS using a URL pattern such as /cgi-bin/IEEE8021x_upload.cgi or check the web server's allowed CGI scripts list if available.Affected if The IEEE8021x_upload.cgi endpoint is exposed and responds to requests without authentication.
-
Verify if unauthenticated multipart upload is allowedSend a crafted multipart HTTP POST request to the IEEE8021x_upload.cgi endpoint with an oversized filename parameter, observing whether the server accepts the request without requiring authentication.Affected if The endpoint accepts unauthenticated multipart upload requests.
A user is affected if they operate a GeoVision GV-LPC2011 or GV-LPC2211 IP camera running firmware V1.12 or earlier with the IEEE8021x_upload.cgi endpoint exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor firmware update to a version beyond V1.12 that contains proper bounds validation for upload filename parameters; if unavailable, restrict external access to the affected CGI endpoint via network segmentation or WAF rules.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57874 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data