CVE-2026-12846
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 · uneditedGV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and RS-485. DVRSearch is a service running by default on the IOBox listening for UDP messages on port 10001. Any user on the network can send messages to this service and interact with it. Upon receiving a UDP message, the server reads at most 1460 bytes into a local buffer and a pointer to the buffer is stored in a global variable: #### Net Mask field stack overflow The following code is vulnerable to a stack overflow that is attacker-controlled: v6 = strlen(g_network_config->net_mask); memcpy(&reply_buf[184], g_network_config->net_mask, v6);
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 confidenceStack-based buffer overflow in the DVRSearch service on GV-I/O Box 4E. The service reads UDP messages (up to 1460 bytes) and copies the attacker-controlled net_mask field into a fixed buffer offset at reply_buf[184] using memcpy without bounds checking. Since the net_mask length is derived from attacker input, a maliciously long net_mask value overflows the stack buffer.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 GV-I/O Box 4E device on the networkCheck your network inventory or physically inspect connected hardware for the GV-I/O Box 4E model. If using network scanning tools, look for devices responding to DVRSearch service probes on UDP port 10001.Affected if The environment contains a GV-I/O Box 4E device.
-
Verify DVRSearch service is activeScan the target device for open UDP port 10001 using a tool like nmap: nmap -sU -p 10001 <target-ip>. Alternatively, check the device documentation or management interface for DVRSearch service status.Affected if The DVRSearch service is running and UDP port 10001 is open on the device.
-
Confirm network exposure of the serviceReview firewall rules and network segmentation to determine if UDP port 10001 is accessible from untrusted network segments. Check if the device is directly exposed to the internet or accessible from guest/VLAN networks.Affected if UDP port 10001 is reachable from network segments that contain untrusted or unauthorized users.
-
Assess firmware versionAccess the device management interface or check the firmware version through the vendor-provided tools. Compare your installed firmware version against any available vendor release notes or security advisories.Affected if The device firmware is older than the vendor fix or no firmware update has been applied.
You are affected if you have a GV-I/O Box 4E with the DVRSearch service running and UDP port 10001 exposed to untrusted network segments.
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 dataNetwork segmentation and firewall rules to restrict unauthorized network access to UDP port 10001. Apply vendor firmware update when available. Consider replacing or upgrading the device if EOL.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12846 — 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-12846 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