Description
When using the Direct XIP
update strategy, the main application image starts other cores (i.e. radio
core), based on the currently active slot without additional verification. The
MCUboot in the bare (upstream) configuration assumes that if there is at least
a single slot for each image available, the system is bootable and continues
the boot process. This may lead to a situation when MCUboot picks different
slot for different images (i.e. (a) for the main application and (b) for the
radio image), boots the main application (from slot (a)) that afterwards starts
the radio image by providing an address of the unauthenticated slot ((a)
instead of (b)).
Published: 2026-09-07
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized code execution on boot
Action: Immediate Patch
AI Analysis

Impact

The vulnerability arises when the MCUBoot bootloader on Nordic Semiconductor nRF54H20 devices, using the Direct XIP update strategy, selects an unauthenticated slot for a secondary image. The bootloader assumes the presence of at least one slot per image is sufficient for a bootable system, causing mismatches between the main application slot and the radio core slot. As a result, after booting the main application, the radio core can be started with an address pointing to an unauthenticated slot. This permits the execution of code that has not been authenticated, compromising the device’s integrity and potentially enabling further attacks. The flaw is identified as CWE‑347, improper handling of input during boot.

Affected Systems

This issue affects devices built with Nordic Semiconductor ASA’s nRF54H20 microcontroller that employ the Direct XIP update strategy. Vendor software that uses the upstream MCUBoot without patching for this behavior is impacted. No specific firmware version ranges are listed, so any product using this bootloader configuration is susceptible.

Risk and Exploitability

The CVSS score is 7.5, indicating a high severity. The EPSS score is not available, so the exploitation probability cannot be quantified. The vulnerability is not listed in CISA KEV. Attackers would need to supply a firmware image with a misleading slot arrangement, suggesting the attack vector is via the firmware update channel or supply chain. Exploitation requires the ability to write to both the main application and radio core storage areas; once achieved, the device will boot unauthenticated code during normal operation.

Generated by OpenCVE AI on September 7, 2026 at 13:55 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest firmware version from Nordic that contains the MCUBoot fix for slot validation.
  • If a new firmware is not yet available, reconfigure the device to disable the Direct XIP update strategy or enforce manual slot selection for the radio core.
  • Verify that all firmware images are signed and that the bootloader performs proper signature verification before selecting slots, to prevent unauthorized code execution.

Generated by OpenCVE AI on September 7, 2026 at 13:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 08 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Nordic Semiconductor Asa
Nordic Semiconductor Asa nrf54h20
Vendors & Products Nordic Semiconductor Asa
Nordic Semiconductor Asa nrf54h20

Tue, 08 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 07 Sep 2026 08:15:00 +0000

Type Values Removed Values Added
Description When using the Direct XIP update strategy, the main application image starts other cores (i.e. radio core), based on the currently active slot without additional verification. The MCUboot in the bare (upstream) configuration assumes that if there is at least a single slot for each image available, the system is bootable and continues the boot process. This may lead to a situation when MCUboot picks different slot for different images (i.e. (a) for the main application and (b) for the radio image), boots the main application (from slot (a)) that afterwards starts the radio image by providing an address of the unauthenticated slot ((a) instead of (b)).
Title nRF54H20: MCUBoot can be tricked to executing unauthenticated code
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Nordic Semiconductor Asa Nrf54h20
cve-icon MITRE

Status: PUBLISHED

Assigner: YesWeHack

Published:

Updated: 2026-09-08T15:00:36.748Z

Reserved: 2026-07-01T09:51:22.466Z

Link: CVE-2026-14296

cve-icon Vulnrichment

Updated: 2026-09-08T15:00:33.721Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-07T08:17:11.773

Modified: 2026-09-09T15:50:19.447

Link: CVE-2026-14296

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-08T20:38:12Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature