zephyrproject-rtos Zephyr up to 4.1.0 BLE Connection Response security check
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in zephyrproject-rtos Zephyr up to 4.1.0 and classified as problematic. Affected by this issue is some unknown functionality of the component BLE Connection Response Handler. This manipulation causes security check. This vulnerability is registered as CVE-2025-10457. The attack requires access to the local network. No exploit is available.
Details
A vulnerability has been found in zephyrproject-rtos Zephyr up to 4.1.0 and classified as problematic. Affected by this vulnerability is an unknown part of the component BLE Connection Response Handler. The manipulation with an unknown input leads to a security check vulnerability. The CWE definition for the vulnerability is CWE-358. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. As an impact it is known to affect availability. The summary by CVE is:
The function responsible for handling BLE connection responses does not verify whether a response is expected—that is, whether the device has initiated a connection request. Instead, it relies solely on identifier matching.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-10457 since 09/15/2025. The exploitation appears to be easy. The attack needs to be done within the local network. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/29/2025). MITRE ATT&CK project uses the attack technique T1211 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-30236). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔒
CNA Base Score: 4.3
CNA Vector (zephyr): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Security checkCWE: CWE-358
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/15/2025 CVE reserved09/19/2025 Advisory disclosed
09/19/2025 VulDB entry created
10/29/2025 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2025-10457 (🔒)
GCVE (CVE): GCVE-0-2025-10457
GCVE (VulDB): GCVE-100-324985
EUVD: 🔒
Entry
Created: 09/19/2025 07:49Updated: 10/29/2025 21:12
Changes: 09/19/2025 07:49 (62), 09/19/2025 08:30 (1), 10/29/2025 21:12 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.