CVE-2026-52199
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 issue in Generic OEM UZ801_v2.1 4G LTE Router V3.4.3 allows a remote attacker to execute arbitrary code via the sbin/adbd component
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 confidenceA remote code execution vulnerability exists in the sbin/adbd component of the Generic OEM UZ801_v2.1 4G LTE Router running firmware version V3.4.3. The adbd (Android Debug Bridge daemon) appears to be exposed or improperly secured, allowing a remote attacker to execute arbitrary code on the affected device with high privilege.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 device model and firmware versionCheck the router's web interface, system settings, or SSH into the device and run 'cat /proc/version' or 'uname -a' to confirm the device is a Generic OEM UZ801_v2.1 4G LTE Router and note the firmware version V3.4.3Affected if The device matches the UZ801_v2.1 model with firmware V3.4.3 or lower unpatched versions
-
Verify adbd service is runningSSH into the device or access via serial console and run 'ps | grep adbd' or 'ps aux | grep adbd' to determine if the Android Debug Bridge daemon process is activeAffected if The adbd process is found running on the device
-
Check if adbd is exposed on network interfacesRun 'netstat -tuln | grep 5555' or 'ss -tuln | grep 5555' to see if the default adbd port (5555) is listening on non-loopback interfaces, indicating network exposureAffected if Port 5555 (or adbd) is listening on an external network interface rather than only localhost/127.0.0.1
-
Inspect adbd configuration and authenticationExamine /etc/default/services.ini, /etc/adb.conf, or similar configuration files if present; check if adbd was started with the '-a' flag (listens on all interfaces) or without authentication enforcementAffected if Adbd is configured to allow connections without authentication or is bound to all interfaces (0.0.0.0)
-
Verify network accessibility of adbdFrom an external host on the same network, run 'adb connect <device_ip>:5555' to test if the device accepts ADB connections without requiring authenticationAffected if The ADB connection succeeds without providing credentials, confirming the service is remotely accessible and exploitable
The device is affected if it is a UZ801_v2.1 4G LTE Router running firmware V3.4.3 (or unpatched) with the adbd service running and exposed on the network without proper authentication controls.
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 firmware update when available; otherwise, disable or restrict access to the adbd service, implement network segmentation to limit exposure, and monitor for indicators of compromise.
- 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-52199 — 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-52199 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