dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-12486

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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 · unedited
Multiple OS command injection vulnerabilities exist in the libNetSetObj.so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted network packet can lead to command execution. An attacker can send a network request to trigger this vulnerability. `libNetSetObj.so` is an internal library used by various binaries on the device to configure the network stack (start and stop various services, configure IP, Netmask, gateway, dns, etc.) #### CNetSetObj::m_F_n_Set_IP_Addr command injection The following function takes a string as an ip address, performs no sanitization and calls `system`. This is a classic command injection vulnerability. The function is reachable from both the network-exposed `DVRSearch` service and the `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_IP_Addr(const char **this, char *ip_addr) { bool v2; // zf char v4[72]; // [sp+0h] [bp-48h] BYREF v2 = *this == 0; if ( *this ) v2 = ip_addr == 0; if ( v2 ) return 0; sprintf(v4, "/sbin/ifconfig %s %s", *this, ip_addr); // attacker controlled ip address system(v4); return 1; }

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 confidence

OS command injection in CNetSetObj::m_F_n_Set_IP_Addr within libNetSetObj.so. The function accepts an IP address parameter and passes it unsanitized directly to sprintf() to construct a shell command, then executes it via system(). The vulnerable function is exposed through both the DVRSearch network service and Network.cgi endpoint, allowing remote attackers to execute arbitrary commands on the device.

MitigationApply vendor firmware patch when available; if no patch exists, disable or restrict network access to DVRSearch and Network.cgi services, or network-segment the device to limit exposure.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate libNetSetObj.so on the system
    Search for the library file: find / -name 'libNetSetObj.so' 2>/dev/null or check common library directories like /lib, /usr/lib, /opt, /app. Note its path and any version information in the filename or associated metadata.
    Affected if The library libNetSetObj.so is present on the system, indicating the vulnerable component is installed.
  2. Identify the firmware or software version
    Check the device firmware version through available interfaces such as: cat /proc/version, cat /etc/version, manufacturer admin panel, or SNMP. Compare the version against any vendor release notes for CVE-2026-12486 patches.
    Affected if The firmware version is unpatched and matches the vulnerable version range for this CVE.
  3. Verify DVRSearch service exposure
    Check if the DVRSearch network service is running and accessible: scan the network for open ports associated with DVR services (commonly 554, 8000-8002, 9000), or check service configuration files for DVRSearch enablement.
    Affected if DVRSearch service is exposed to the network without proper access restrictions.
  4. Verify Network.cgi endpoint accessibility
    Check if Network.cgi is accessible on the web server: attempt to access the CGI endpoint (typically found at /cgi-bin/Network.cgi or similar paths) from authorized network segments, or review web server configuration for CGI script mappings.
    Affected if Network.cgi endpoint is accessible and accepts IP address parameters without authentication or input validation.

The system is affected if libNetSetObj.so is present, the firmware is unpatched, and either the DVRSearch service or Network.cgi endpoint is exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; if no patch exists, disable or restrict network access to DVRSearch and Network.cgi services, or network-segment the device to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12486 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12486 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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