{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-14296 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-14296 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-14296 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-14296 in the wild and no public exploit code.\n\nAffected product: Nordic Semiconductor ASA nRF54H20. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-14296/ (Markdown: https://insights.sbomify.com/CVE-2026-14296/index.md)","id":"CVE-2026-14296","markdown":"https://insights.sbomify.com/CVE-2026-14296/index.md","name":"CVE-2026-14296","record":{"aliases":["GHSA-j59p-mqmr-fcgh"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"nRF54H20 firmware","requires_auth":"none","summary":"Attackers can bypass MCUBoot authentication to execute unauthenticated code on the radio core by exploiting slot selection logic in Direct XIP updates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"YesWeHack","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"When using the Direct XIP\nupdate strategy, the main application image starts other cores (i.e. radio\ncore), based on the currently active slot without additional verification. The\nMCUboot in the bare (upstream) configuration assumes that if there is at least\na single slot for each image available, the system is bootable and continues\nthe boot process. This may lead to a situation when MCUboot picks different\nslot for different images (i.e. (a) for the main application and (b) for the\nradio image), boots the main application (from slot (a)) that afterwards starts\nthe radio image by providing an address of the unauthenticated slot ((a)\ninstead of (b)).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"nRF54H20: MCUBoot can be tricked to executing unauthenticated code","id":"CVE-2026-14296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in nRF Connect SDK","id":"CVE-2026-14297"},"packages":[],"prev":{"headline":"Autopay / Blue Media for WooCommerce \u003c 5.0.1 - Unauthenticated Stored XSS via CSS Editor","id":"CVE-2026-14293"},"products":["nRF54H20"],"published":"2026-09-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["Nordic Semiconductor ASA"]},"summary":"Attackers can bypass MCUBoot authentication to execute unauthenticated code on the radio core by exploiting slot selection logic in Direct XIP updates.","url":"https://insights.sbomify.com/CVE-2026-14296/"}