Cyber Resilience

CVE-2025-64983

Published
26 November 2025
Modified
15 April 2026
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0030 23th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2025-64983 is a high-severity Active Debug Code (CWE-489) vulnerability in Jvn (inferred from references). Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

Smart Video Doorbell firmware versions prior to 2.01.078 contain an active debug code vulnerability that allows an attacker to connect via Telnet and gain access to the device.

CWE(s)
CWE-489

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-49188Shared CWE-489
CVE-2024-53648Shared CWE-489
CVE-2024-28008Shared CWE-489
CVE-2025-54660Shared CWE-489
CVE-2024-46873Shared CWE-489
CVE-2023-32645Shared CWE-489
CVE-2025-42872Shared CWE-489
CVE-2024-31406Shared CWE-489
CVE-2026-40035Shared CWE-489
CVE-2026-54799Shared CWE-489

Affected Assets

Jvn
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CM-2 Baseline Configuration partial match

Baseline configuration defines the approved production state that must exclude active debug code.

CM-7 Least Functionality partial match

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can require removal of debug code before release.

SA-3 System Development Life Cycle partial match

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance catches active debug code before deployment.

A.8.9 Configuration management mostly match
prevents

Configuration management can disable or remove debug features through hardened baselines.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates removal of debug code before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

A.8.31 Separation of development, test and production environments partial match
prevents

Separation of environments reduces risk of debug code reaching production but does not directly address its removal.

A.8.32 Change management partial match
prevents

Change management can enforce removal of debug code as part of release gates.

References