# CVE-2026-14296: nRF54H20: MCUBoot can be tricked to executing unauthenticated code

> Attackers can bypass MCUBoot authentication to execute unauthenticated code on the radio core by exploiting slot selection logic in Direct XIP updates.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-j59p-mqmr-fcgh

## What is CVE-2026-14296?

CVE-2026-14296 is a high-severity vulnerability in Nordic Semiconductor ASA nRF54H20, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)).

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-14296?


## How do I fix CVE-2026-14296?

No fix has been published for CVE-2026-14296 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14296 being exploited?

There is no known exploitation of CVE-2026-14296 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14296 and fix it if it is affected.

What it is: CVE-2026-14296 is a high-severity vulnerability in Nordic Semiconductor ASA nRF54H20, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14296 in the wild and no public exploit code.

Affected product: Nordic Semiconductor ASA nRF54H20. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14296/ (Markdown: https://insights.sbomify.com/CVE-2026-14296/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14296
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14296
- OSV: https://osv.dev/vulnerability/CVE-2026-14296

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14296/
Summaries are generated and may contain mistakes; the official description above is the record.