CVE-2026-19741: auth in zephyrproject zephyr
Description
Zephyr's OpenThread integration used a default, publicly known Joining Device Credential (PSKd) "J01NME" when the joiner autostart feature was enabled but the PSKd was not overridden. This allowed an attacker within radio range to authenticate as a commissioner and provision the device with a malicious operational dataset, effectively taking control of the device's Thread network connection. The vulnerability affects Zephyr versions from 1.14.0 up to but not including 4.5.0. A fix was implemented to remove the default PSKd and enforce build-time checks requiring a unique PSKd when joiner autostart is enabled.
CVSS v3.1
Score 7.5high
Affected software
zephyrproject
zephyr
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Zephyr's OpenThread integration defined a default PSKd "J01NME" used for Thread commissioning authentication. If a firmware image was built with CONFIG_OPENTHREAD_JOINER_AUTOSTART=y and the PSKd was not overridden, the device shipped with this publicly known credential. An attacker within 802.15.4 radio range could use any Thread commissioner registered with "J01NME" to complete the DTLS-PSK handshake, supply a malicious operational dataset, and take control of the device's Thread network connection. This allows the attacker to intercept, drop, inject, and spoof IPv6 traffic, effectively isolating the device from its intended network. The vulnerability only affects builds enabling joiner autostart with the default PSKd left unchanged, which is not the default configuration and not used in in-tree samples. The fix removes the default PSKd and adds a build assertion to require a unique PSKd when autostart is enabled, encouraging per-device provisioning of PSKd and manual start of the joiner.
Potential Impact
An unauthenticated attacker within radio range can impersonate a Thread commissioner using the default PSKd and provision the device with a malicious operational dataset. This compromises the device's network integrity, allowing the attacker to control its Thread network participation, intercept and manipulate IPv6 traffic, and isolate the device from its intended network. Application-layer security with independent credentials remains unaffected. The exposure is limited to devices built with joiner autostart enabled and the default PSKd unchanged.
Mitigation Recommendations
A fix is available that removes the default PSKd and adds a build-time assertion requiring a unique PSKd when joiner autostart is enabled. Products should provision a unique per-device PSKd from factory data and avoid relying on the default credential. Additionally, applications should start the joiner manually rather than relying on autostart. Users should upgrade to Zephyr version 4.5.0 or later where this fix is included.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-08-13T13:46:35.935Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6adbbe27d73cc49347b8fb60
Added to database: 10/23/2026, 20:05:59 UTC
Last enriched: 10/23/2026, 20:20:23 UTC
Last updated: 10/23/2026, 20:21:17 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.