Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical device access
-
DeliveryAttach glitching probes to power/clock lines
-
ExploitProfile target boot or crypto routine timing
-
ExecutionInject precisely timed voltage or clock fault
-
PersistBypass security check (e.g., signature verification)
-
ImpactExecute unauthorized code with full hardware privileges
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Physical proximity to the target hardware is mandatory (AV:P); remote exploitation is not possible. The attacker must have access to the device's power supply or clock lines, typically requiring opening the device enclosure and attaching probes or hardware implants. High attack complexity (AC:H) means specialized fault injection equipment, precise timing knowledge of the target's boot or cryptographic routines, and iterative calibration are required - exploitation is not automated or trivially repeatable without device-specific profiling. No prior authentication or software privileges are required (PR:N) once physical access is achieved. Exploitation is most impactful when the SAMA5D4 is used as a root of trust (secure boot, key storage), as compromising that role undermines all higher-layer security guarantees. Devices with intact physical tamper protection, debug port lockdown, or voltage/frequency anomaly detection hardware limit exploitation feasibility. |
| Impact | Real-world risk is substantially constrained by the physical access requirement (AV:P) and high attack complexity (AC:H). Exploitation requires specialized glitching hardware, oscilloscopes or FPGAs for timing calibration, and considerable expertise in fault injection techniques - this is not a script-kiddie attack surface. The CVSS 4.0 score of 7.3 reflects this: despite all-high vulnerable-system and subsequent-system impacts, the physical and complexity barriers keep the score out of the critical tier. No CISA KEV listing and no public POC corroborate the assessment that this is currently a targeted, nation-state or sophisticated hardware lab-level threat rather than a broadly opportunistic one. The elevated subsequent-system impact metrics (SC:H/SI:H/SA:H) are significant: if the SAMA5D4 acts as a root of trust for a larger platform, compromising it cascades to all software and data it protects. Defenders should prioritize physical security of devices over remote patch urgency. Missing data: no patched hardware revision or firmware mitigation version is identified from the reference. |
| Exploit ScenarioDerived | An attacker with physical access to a product built on the SAMA5D4 - such as an industrial controller or IoT gateway - connects a voltage glitching rig (e.g., a ChipWhisperer or custom FPGA-based tool) to the power rails, then sends precisely timed transient faults during the secure boot signature verification routine. The fault causes the processor to skip or corrupt the conditional branch that checks the signature result, allowing unsigned or malicious firmware to be accepted as authentic and executed with full privileges. No public POC has been identified, but the attack methodology is well-documented in academic fault injection literature and is within reach of a determined hardware attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
Hardware fault injection via voltage and clock glitching in the Microchip SAMA5D4 ARM Cortex-A5 microprocessor enables a physically proximate attacker to subvert security-critical operations such as secure boot, cryptographic key protection, and privilege enforcement. All versions of the SAMA5D4 are affected per the vendor's CPE entry, and Microchip self-reported this vulnerability. No public exploit code has been identified and CISA has not added this to the KEV catalog, but the all-high impact scores in the CVSS 4.0 vector (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) reflect that successful exploitation grants total control over the affected system and any downstream components it secures.
RemediationAI
No vendor-released patch identified at time of analysis; this is a hardware-rooted vulnerability and remediation options differ from software CVEs. The primary Microchip advisory should be consulted at https://www.microchip.com/en-us/solutions/technologies/embedded-security/how-to-report-potential-product-security-vulnerabilities/sama5d44-fault-injection-vulnerability for any issued guidance, errata, or recommended design changes. As compensating controls, system designers should implement physical tamper detection (epoxy encapsulation, active mesh shields, voltage and frequency monitors external to the SoC) that trigger secure wipe or lockout on anomaly detection - trade-off is added BOM cost and potential false-positive lockouts in electrically noisy environments. Restrict physical access to deployed devices through enclosures with tamper-evident seals and, where applicable, enforce Debug Access Port (DAP) lockdown via fuse configuration to reduce the fault injection attack surface. Firmware-level mitigations such as redundant security checks, software-based glitch detection loops, and hardening of critical conditional branches can raise the bar but cannot fully compensate for absent hardware countermeasures.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The SAMA5D4 (cpe:2.3:a:microchip:sama5d4:*:*:*:*:*:*:*:*) is an ARM Cortex-A5-based application microprocessor from Microchip Technology, designed for embedded security use cases including secure boot, hardware cryptographic acceleration, and tamper-resistant key storage. CWE-1247 - 'Improper Protection Against Voltage and Clock Glitches' - describes a class of hardware vulnerability in which the chip lacks sufficient countermeasures (e.g., voltage detectors, clock monitors, redundant logic) to detect or recover from transient faults deliberately induced in the power supply or clock lines. By injecting precisely timed voltage spikes or clock perturbations, an attacker can cause the processor to skip instructions, corrupt branch outcomes, or induce faults in cryptographic computations, effectively bypassing security gates implemented in hardware or firmware.
Know when Sama5D4 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Physical access and specialized glitching equipment required (AV:P, AC:H); scope changes to downstream trusted systems (S:C); all CIA impacts high once glitch succeeds.
Primary rating from Vendor (Microchip).
CVSS VectorVendor: Microchip
DescriptionCVE.org
Improper protection against voltage and clock glitches vulnerability in Microchip SAMA5D4 allows Hardware Fault Injection.
This issue affects SAMA5D4.
Executive ViewAI
Microchip SAMA5D4 microprocessors are vulnerable to hardware-based fault injection attacks that can bypass secure boot and compromise cryptographic key protection in all deployed versions. An attacker with physical access to affected devices can gain complete control over the processor and any systems it secures, impacting any organization whose critical infrastructure or security-sensitive devices rely on this chip.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict physical access to affected devices through facility controls (card-access doors, surveillance), deploy tamper-detection mechanisms, segregate sensitive systems to low-access environments, and consider network isolation for systems where physical compromise is a realistic threat vector.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
EUVD-2026-64951
GHSA-8c5x-7fmx-f5j4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB