dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-28747

HIGH · 7.1 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
A weak key generation vulnerability exists in specific firmware versions of Milesight AIOT cameras allows authorization to be bypassed.

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 confidence

Weak key generation in Milesight AIOT camera firmware allows attackers to bypass authorization. The cryptographic key generation mechanism uses insufficient entropy or predictable values, enabling unauthorized access to camera functions.

MitigationUpdate to patched firmware versions when available. If no patch exists, restrict network access to cameras and monitor for unauthorized access attempts.

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
Adjacent
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm device is a Milesight AIOT camera
    Identify the device model through the web interface, physical label, or SNMP/network discovery. This vulnerability affects only Milesight AIOT camera models.
    Affected if The device is not a Milesight AIOT camera model, as the weak key generation issue is specific to this product line.
  2. Locate the firmware version
    Access the camera web interface under Settings > System > About or check via the manufacturer's discovery tool or SNMP. Compare your installed firmware version to any affected version ranges provided by Milesight security advisories.
    Affected if The installed firmware version falls within an affected range if such ranges are published by Milesight.
  3. Verify network exposure
    Check the camera network configuration to determine if it is directly accessible from untrusted networks such as the public internet or shared guest networks.
    Affected if The camera is reachable from untrusted networks, as the weak key flaw enables remote authorization bypass.
  4. Review admin accounts and access logs
    Inspect the camera admin user list for any unauthorized accounts and review access logs for unexpected administrative sessions, especially from external IP addresses.
    Affected if Unexpected admin accounts exist or administrative access from untrusted sources is logged.

You are affected if you have a Milesight AIOT camera with firmware known to have weak key generation, especially if the device is network-accessible from untrusted segments.

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

Update to patched firmware versions when available. If no patch exists, restrict network access to cameras and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28747 — 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-28747 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