CVE-2025-10457

CVE-2025-10457 is a medium-severity vulnerability in Zephyrproject Zephyr with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-358.

Key facts

Description

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.

Frequently asked questions

What is CVE-2025-10457?
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.
How severe is CVE-2025-10457?
CVE-2025-10457 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over an adjacent network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2025-10457 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-10457?
CVE-2025-10457 affects Zephyrproject Zephyr. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-10457?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-10457 have an EU (EUVD) identifier?
Yes. CVE-2025-10457 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-30236.
When was CVE-2025-10457 published?
CVE-2025-10457 was published on 2025-09-19 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Zephyrproject Zephyr

All CVEs affecting Zephyrproject Zephyr →

Other CWE-358 vulnerabilities

Browse all CWE-358 vulnerabilities →