CVE-2025-10458 json
Bluetooth: le_conn_rsp does not sanitize CID, MTU, MPS values
published last yr. modified 29d ago also EUVD-2025-30239
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
Parameters are not validated or sanitized, and are later used in various internal operations.
Is CVE-2025-10458 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
| NVD | 3.1 | 7.6 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
Affected products
- zephyrproject-rtos Zephyr
Classification
- Weakness
-
- CWE-130 Improper Handling of Length Parameter Inconsistency
References
Sources
- CVE List CVE-2025-10458
- NVD CVE-2025-10458
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.