CVE-2026-34005
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 · uneditedIn Sofia on Xiongmai DVR/NVR (AHB7008T-MH-V2 and NBD7024H-P) 4.03.R11 devices, root OS command injection can occur via shell metacharacters in the HostName value via an authenticated DVRIP protocol (TCP port 34567) request to the NetWork.NetCommon configuration handler, because system() is used.
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 confidenceAuthenticated OS command injection in Xiongmai DVR/NVR devices (AHB7008T-MH-V2, NBD7024H-P) running firmware 4.03.R11. An attacker with valid DVRIP credentials can inject shell metacharacters into the HostName parameter sent to the NetWork.NetCommon configuration handler on TCP port 34567, where the unsafe use of system() executes arbitrary commands with root privileges.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 the device modelCheck the DVR/NVR device model through its web interface, label on the device, or SNMP query. Look for AHB7008T-MH-V2 or NBD7024H-P, or other Xiongmai-based devices.Affected if The device is an AHB7008T-MH-V2 or NBD7024H-P model (or other Xiongmai DVR/NVR device).
-
Check the firmware versionAccess the device web interface (usually via HTTP on port 80/8080) and navigate to System > Information, or use the DVRIP protocol on port 34567 to query device info. Look for firmware version 4.03.R11.Affected if The firmware version is 4.03.R11 (or versions not later than the patched release).
-
Verify TCP port 34567 is exposedPerform a port scan of the device on TCP port 34567 (e.g., nmap -p 34567 <device-ip> or telnet <device-ip> 34567).Affected if Port 34567 is open and accessible from an untrusted network.
-
Confirm remote management is enabledCheck if the NetWork.NetCommon configuration handler is accessible by attempting to connect to the DVRIP service on port 34567, or verify remote management is enabled in the device network settings.Affected if Remote management via DVRIP protocol on port 34567 is enabled and accepts connections.
You are affected if you operate an Xiongmai DVR/NVR (specifically AHB7008T-MH-V2 or NBD7024H-P) running firmware 4.03.R11 with TCP port 34567 exposed and accessible, and an attacker could obtain valid DVRIP credentials.
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 dataImmediately restrict access to TCP port 34567 via firewall rules to trusted management IPs only, or isolate affected devices in a separate VLAN. Contact Xiongmai for patched firmware and apply once available.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34005 — 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-34005 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