Cyber Resilience

CVE-2026-36027

Published
08 July 2026
Modified
10 July 2026
CVSS Score v3.1 6.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0033 26th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2026-36027 is a medium-severity Hardware Allows Activation of Test or Debug Logic at Runtime (CWE-1313) vulnerability in Code (inferred from references). Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 26th 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 SA-18 (Tamper Resistance and Detection) and SC-51 (Hardware-based Protection) — see the control section below for these in your framework.

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

An issue in Code27 Companion Hub SQ3A.220705.003.A1 allows a physically proximate attacker to execute arbitrary code via the USB debugging (ADB) and Android Debug Bridge components

CWE(s)
CWE-1313

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-2919Shared CWE-1313

Affected Assets

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

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-18 Tamper Resistance and Detection partial match

Anti-tamper requirements on developers stop hardware debug features from being activatable at runtime.

SC-51 Hardware-based Protection partial match

Hardware-enforced write protection and procedures directly block unauthorized runtime activation of debug or test logic.

SR-9 Tamper Resistance and Detection partial match

Supply-chain tamper-resistance program prevents introduction of hardware that permits runtime debug activation.

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.

ID.RA-09 mostly match
prevents

Pre-acquisition hardware integrity assessment directly prevents introduction of devices with exposed debug logic.

GV.SC-07 partial match
prevents

Supplier-product risk assessment can identify and respond to hardware debug-feature exposure risks.

PR.PS-03 partial match
prevents

Hardware replacement policy can remove affected devices after discovery but does not prevent the weakness itself.

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 includes verification that debug interfaces are disabled or protected before release.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require disabling or locking debug/test logic in production hardware.

A.8.32 Change management none match
none

Change management processes can enforce configuration baselines that disable runtime debug features.

A.8.9 Configuration management none match
mitigates

Configuration management can mandate secure hardware settings that prevent activation of test/debug logic.

References