CWE · MITRE source
CWE-1300Improper Protection of Physical Side Channels
The device does not contain sufficient protection mechanisms to prevent physical side channels from exposing sensitive information due to patterns in physically observable phenomena such as variations in power consumption, electromagnetic emissions (EME), or acoustic emissions.
An adversary could monitor and measure physical phenomena to detect patterns and make inferences, even if it is not possible to extract the information in the digital domain. Physical side channels have been well-studied for decades in the context of breaking implementations of cryptographic algorithms or other attacks against security features. These side channels may be easily observed by an adversary with physical access to the device, or using a tool that is in close proximity. If the adversary can monitor hardware operation and correlate its data processing with power, EME, and acoustic measurements, the adversary might be able to recover of secret keys and data.
Last updated: 20 August 2026 13:14 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 1 framework(s): CAPEC 2 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
- 2 hardening rules · 1 OS baseline
—
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-10890 | 6.8 | 9.1 | 0.0029 | 2025-09-24 |
CVE-2026-11153 UPD | 6.7 | 9.1 | 0.0026 | 2026-06-04 |
CVE-2023-6258 UPD | 6.2 | 8.1 | 0.0056 | 2024-01-30 |
CVE-2026-13790 | 5.1 | 6.5 | 0.0039 | 2026-06-30 |
CVE-2026-13922 | 5.1 | 6.5 | 0.0039 | 2026-06-30 |
CVE-2026-13935 | 5.1 | 6.5 | 0.0039 | 2026-06-30 |
CVE-2025-11207 | 5.0 | 6.5 | 0.0025 | 2025-11-06 |
CVE-2026-5876 UPD | 5.0 | 6.5 | 0.0025 | 2026-04-08 |
CVE-2026-11284 UPD | 5.0 | 6.5 | 0.0024 | 2026-06-05 |
CVE-2026-13809 | 5.0 | 6.5 | 0.0036 | 2026-06-30 |
CVE-2026-14071 | 5.0 | 6.5 | 0.0024 | 2026-06-30 |
CVE-2026-14074 | 5.0 | 6.5 | 0.0029 | 2026-06-30 |
CVE-2026-14085 | 5.0 | 6.5 | 0.0026 | 2026-06-30 |
CVE-2026-17796 | 5.0 | 6.5 | 0.0030 | 2026-07-30 |
CVE-2026-17800 | 5.0 | 6.5 | 0.0030 | 2026-07-30 |
CVE-2026-11289 UPD | 4.9 | 6.5 | 0.0020 | 2026-06-05 |
CVE-2025-11210 | 4.2 | 5.4 | 0.0022 | 2025-11-06 |
CVE-2026-14012 | 4.1 | 5.3 | 0.0021 | 2026-06-30 |
CVE-2026-17914 | 4.1 | 5.3 | 0.0022 | 2026-07-30 |
CVE-2026-17978 | 4.1 | 5.3 | 0.0021 | 2026-07-30 |
CVE-2025-13992 | 3.6 | 4.7 | 0.0018 | 2025-12-03 |
CVE-2026-17696 | 3.6 | 4.3 | 0.0029 | 2026-07-30 |
CVE-2026-17730 | 3.6 | 4.3 | 0.0024 | 2026-07-30 |
CVE-2026-17760 | 3.6 | 4.3 | 0.0024 | 2026-07-30 |
CVE-2026-17851 | 3.6 | 4.3 | 0.0026 | 2026-07-30 |