Pending AnalysisCVE-2026-27785

CVE-2026-27785: Hardcoded Credentials in Milesight AIOT Camera

Platform

linux

Component

milesight-ms-cxx63-pd

CVE-2026-27785 identifies a critical security flaw within Milesight MS-Cxx63-PD AIOT Camera Firmware. This vulnerability stems from the presence of hardcoded credentials, granting attackers potentially unrestricted access to the camera and its associated data. The affected firmware versions include those from 0.0.0 through T63.8.0.4LPR-r3. A firmware update is necessary to resolve this issue.

Impact and Attack Scenarios

The presence of hardcoded credentials within the Milesight AIOT camera firmware presents a severe security risk. An attacker who discovers these credentials can gain complete control over the camera, including access to live video feeds, recorded footage, and configuration settings. This could lead to unauthorized surveillance, data theft, and potential manipulation of the camera's functionality. Furthermore, compromised cameras can be leveraged as entry points for lateral movement within a network, potentially impacting other connected devices and systems. The blast radius extends to any sensitive data or systems accessible through the camera.

Exploitation Context

CVE-2026-27785 was published on 2026-04-27. The vulnerability's severity is rated HIGH (CVSS: 8.8). There is currently no indication of this vulnerability being actively exploited in the wild. Public proof-of-concept (POC) code is not yet available, but the nature of hardcoded credentials makes it likely that exploits will emerge. Monitor CISA and NVD advisories for updates.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureMedium

EPSS

0.02% (5% percentile)

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H8.8HIGHAttack VectorAdjacentHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredNoneAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityHighRisk of sensitive data exposureIntegrityHighRisk of unauthorized data modificationAvailabilityHighRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Adjacent — requires network proximity: same LAN, Bluetooth, or local wireless segment. Not internet-exposed.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
None — unauthenticated. No login or credentials needed to exploit.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
Integrity
High — attacker can write, modify, or delete any data: databases, config files, or code.
Availability
High — complete crash or resource exhaustion. Full denial of service.

Affected Software

Componentmilesight-ms-cxx63-pd
VendorMilesight
Minimum version0.0.0
Maximum versionT_63.8.0.4_LPR-r3

Weakness Classification (CWE)

Timeline

  1. Published
  2. Modified
  3. EPSS updated

Mitigation and Workarounds

The primary mitigation for CVE-2026-27785 is to upgrade the Milesight MS-Cxx63-PD AIOT Camera Firmware to a version that addresses the hardcoded credentials issue. Unfortunately, a fixed version is not yet specified. Until a patch is available, consider isolating the camera from the network to prevent unauthorized access. Implement strict network segmentation to limit the potential impact of a compromise. Monitor network traffic for unusual activity originating from the camera's IP address. Review and strengthen password policies for all other network devices to prevent lateral movement. After upgrade, confirm by attempting to access the camera's configuration interface with known, strong credentials.

How to fix

Actualice el firmware de la cámara Milesight MS-Cxx63-PD a una versión corregida que no contenga las credenciales codificadas. Consulte la página de soporte de Milesight para obtener las últimas versiones de firmware y las instrucciones de actualización.

Frequently asked questions

What is CVE-2026-27785 — Hardcoded Credentials in Milesight AIOT Camera?

CVE-2026-27785 is a HIGH severity vulnerability affecting Milesight MS-Cxx63-PD AIOT Camera Firmware versions 0.0.0–T63.8.0.4LPR-r3. It involves hardcoded credentials, allowing unauthorized access to the camera and its data.

Am I affected by CVE-2026-27785 in Milesight AIOT Camera?

If you are using Milesight MS-Cxx63-PD AIOT Camera Firmware versions between 0.0.0 and T63.8.0.4LPR-r3, you are potentially affected by this vulnerability. Check your firmware version immediately.

How do I fix CVE-2026-27785 in Milesight AIOT Camera?

The recommended fix is to upgrade to a patched firmware version. Unfortunately, a fixed version is not yet specified. Until a patch is available, isolate the camera from the network.

Is CVE-2026-27785 being actively exploited?

There is currently no indication that CVE-2026-27785 is being actively exploited in the wild, but the nature of hardcoded credentials makes exploitation likely.

Where can I find the official Milesight advisory for CVE-2026-27785?

Refer to the Milesight website and security advisories for updates and information regarding CVE-2026-27785. Monitor CISA and NVD for updates as well.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Try it now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...