CVE-2025-36529
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 OS command injection issue exists in multiple versions of TB-eye network recorders and AHD recorders. If this vulnerability is exploited, an arbitrary OS command may be executed by an attacker who is logging in to the device.
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 · moderate confidenceThis is an OS command injection vulnerability in TB-eye network video recorders (NVRs) and AHD recorders. An authenticated attacker who can log into the device management interface can inject and execute arbitrary operating system commands, potentially gaining full control of the device and the network segment it resides on.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 TB-eye NVR or AHD recorder devices on your networkReview your network device inventory or scan for devices with TB-eye firmware signatures. Check device labels, management interfaces, or SNMP/syslog banners for 'TB-eye' branding.Affected if Your environment contains any TB-eye branded NVR or AHD recorder devices.
-
Confirm management interface is accessibleAttempt to reach the device web interface on common ports (80, 443, 8080). Check firewall rules and network access control lists for exposure to untrusted networks.Affected if The device management interface is reachable from network segments that contain untrusted or internet-facing systems.
-
Verify authentication configurationCheck whether the device uses default administrative credentials or allows anonymous access to the command injection endpoint. Review user accounts configured on the device.Affected if Default credentials are still in use or the device permits authentication with weak/blank passwords.
-
Check for abnormal device behaviorReview device logs for unexpected commands, unusual process execution, or signs of prior compromise. Look for shell command patterns in HTTP requests or system logs.Affected if Logs show execution of unrecognized commands or shell interactions that did not originate from legitimate administrator sessions.
You are affected if you have TB-eye NVR or AHD recorders with their management interfaces exposed to untrusted networks using default or weak credentials, or if device logs show evidence of unauthorized command execution.
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 vendor-supplied firmware patches when available. If no patch exists, consider network segmentation to isolate recorder devices and restrict management interface access to trusted IP addresses only.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36529 — 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-2025-36529 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