Cyber Resilience

CVE-2026-51977

Exposed Creds

Published
17 August 2026
Modified
18 August 2026
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2026-51977 is a critical-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 21th 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 SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An issue in Trueview T18061 WiFi 3MP Robot Pan-Tilt Security Camera Version 1.0 allows a physically proximate attacker to escalate privileges via the RSA private key component

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-11781Shared CWE-321
CVE-2025-22455Shared CWE-321
CVE-2023-32169Shared CWE-321
CVE-2026-14932Shared CWE-321
CVE-2025-56577Shared CWE-321
CVE-2025-35052Shared CWE-321
CVE-2025-67305Shared CWE-321
CVE-2026-50226Shared CWE-321
CVE-2026-34635Shared CWE-321
CVE-2025-30095Shared CWE-321

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.

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 activities such as code review and secret scanning directly prevent embedding static keys.

PR.DS-01 partial match
prevents

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

PR.DS-02 partial match
prevents

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

PR.PS-01 partial match
prevents

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

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.

prevents

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

References