CVE-2026-12848 — GV-I/O Box DVRSearch UDP Stack-Based Buffer Overflow (CVE-2026-12848)
GV-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: #### DNS field stack overflow The following code is vulnerable to a stack overflow that is attacker-controlled: v8 = strlen(g_network_config->dns_addr); memcpy(&reply_buf[248], g_network_config->dns_addr, v8);
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Geovision GV-I/O Box 4E).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Geovision | GV-I/O Box 4E | version V2.09 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 3.1 | Critical | 3.9 | 6.0 | 0df08a0e-a200-4957-9bb0-084f562506f9 via NIST National Vulnerability Database |
| 10.0 | CVSS 3.1 | Critical | — | — | GV via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: 0df08a0e-a200-4957-9bb0-084f562506f9) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.60%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Analysis and videos
CVE-2026-12848: GV-I/O Box DVRSearch UDP Stack-Based Buffer Overflow
CVE-2026-12848 is a critical stack-based buffer overflow (CWE-121) in the DVRSearch UDP service of the GV-I/O Box, an embedded device with inputs and relay outputs. The CNA assigns a CVSS 3.1 base score of 10.0, and the record indicates that network users can reach the vulnerable service. The record lists no affected or fixed versions and no KEV listing, so exposure assessment and vendor contact are the immediate priorities.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · geovision inc./gv-i/o box 4e
- SSVC assessment updated
- Record published
- CVSS changed · 10.0
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-12850 GeoVision GV-I/O Box 4E OS Command Injection in libNetSetObj.so Jun 24, 2026
- Critical CVE-2026-12851 GeoVision GV-I/O Box 4E OS command injection in libNetSetObj.so Jun 24, 2026
- Critical CVE-2026-12846 GeoVision GV-I/O Box 4E: stack buffer overflow in DVRSearch service Jun 24, 2026
- Critical CVE-2026-12486 GeoVision GV-I/O Box 4E OS Command Injection in libNetSetObj.so Jun 24, 2026
- Critical CVE-2026-12849 GeoVision GV-I/O Box 4E OS Command Injection in libNetSetObj.so Jun 24, 2026
- Critical CVE-2026-12847 GV-I/O Box 4E DVRSearch Stack Buffer Overflow Jun 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-12848 is "GV-I/O Box DVRSearch UDP Stack-Based Buffer Overflow (CVE-2026-12848)", rated Critical. It affects GV-I/O Box 4E (Geovision); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 10.0 describes technical severity. EPSS 0.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.