CVE-2026-36742
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 · uneditedHiseeu C90 v5.7.15 is vulnerable to Insecure Permissions. The UART bootloader is accessible when battery is disconnected (hidden/debug mode).
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 confidenceThe Hiseeu C90 v5.7.15 camera firmware has insecure permission controls that allow UART bootloader access when the battery is disconnected, effectively enabling a hidden/debug mode. An attacker with physical access could potentially interact with the bootloader to dump firmware, modify configurations, or gain elevated 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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 modelLocate the device label, packaging, or web interface to confirm the model is Hiseeu C90Affected if The device is a Hiseeu C90 camera
-
Check the installed firmware versionAccess the camera's web interface or administrative panel and navigate to System > Version Information to view the firmware build numberAffected if The firmware version is exactly v5.7.15
-
Verify physical security of the deviceInspect the device location to determine if it is in a publicly accessible or unsecured area where an attacker could gain physical accessAffected if The device is deployed in an area with unrestricted physical access
-
Inspect for exposed UART interfaceExamine the device exterior and any accessible compartments for exposed pins, connectors, or test points labeled TX/RX or suggesting UART interfaceAffected if UART pins or connector is physically accessible on the device exterior or inside battery compartment
-
Check battery removal behaviorPower the device by battery only, then disconnect the battery and observe if the device remains operational or if bootloader becomes accessible via UARTAffected if Device allows UART bootloader interaction when running on battery and battery is disconnected
A user is affected if they have a Hiseeu C90 camera running firmware v5.7.15 deployed in a location with physical access risk and the device exposes UART functionality when the battery is disconnected.
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 dataRestrict physical access to the device; implement password protection or disable the UART bootloader in production firmware; add tamper detection mechanisms to trigger secure wipe when the battery is removed.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36742 — 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-36742 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