tools: Update nrfutil device to 2.15.7

[jangalda-nsc]

Update nrfutil device to version 2.15.7

[Copilot]

Pull request overview

This PR updates the nrfutil device subcommand from version 2.15.6 to 2.15.7 across all supported platforms (Windows, Linux, and macOS).

• Updates nrfutil device version from 2.15.6 to 2.15.7

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
scripts/tools-versions-win10.yml	Updates nrfutil device version for Windows platform
scripts/tools-versions-linux.yml	Updates nrfutil device version for Linux platform
scripts/tools-versions-darwin.yml	Updates nrfutil device version for macOS platform

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[NordicBuilder]

CI Information

^{To view the history of this post, click the 'edited' button above}
Build number: 9

Inputs:

Sources:

sdk-nrf: PR head: a8b449f72b83cee874f4c5ef34d8f8f165d9f417

more details

sdk-nrf:

PR head: a8b449f72b83cee874f4c5ef34d8f8f165d9f417
merge base: d6c88a74779647f151672a83b995215491d0df9a
target head (main): a61a7f641240ecccc8519af80b3e9d42d8f21f20
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (5)

scripts
│  ├── pip-audit-whitelist.yml
│  ├── requirements-fixed.txt
│  ├── tools-versions-darwin.yml
│  ├── tools-versions-linux.yml
│  │ tools-versions-win10.yml

Outputs:

Toolchain

Version: 400c6cb4ec
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:400c6cb4ec_5ea73affbf

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ✅ Toolchain
• ✅ Build twister
• ✅ Integration tests
  • ✅ test-fw-nrfconnect-ble_mesh
  • ⚠️ doc-internal

Disabled integration tests

• • test-fw-nrfconnect-nrf_lrcs_mosh
  • desktop52_verification
  • test_ble_nrf_config
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread-main
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[github-actions]

You can find the documentation preview for this PR here.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The newly whitelisted CVE-2025-69277 lacks documentation explaining why this security vulnerability is acceptable to whitelist. Consider adding a comment describing the rationale, affected package, and mitigation strategy.

Suggested change

	- GHSA-f83h-ghpp-7wcc
	- GHSA-f83h-ghpp-7wcc
	# CVE-2025-69277: affects a transitive, dev-only dependency used in CI tooling rather than in
	# production workloads. Internal security review determined the vulnerable code path is not
	# reachable in our usage because the tool does not process untrusted input and runs in an
	# isolated environment.
	# Mitigation: production images use a non-vulnerable version of the affected package, and this
	# whitelist entry is limited to CI to avoid noisy pip-audit failures while we keep the tooling
	# version pinned. Reassess on major tooling upgrades.