Which CVEs affect NimBLE 1.9.0?
| CVE | Severity | CVSS | Fixed from | Note |
|---|---|---|---|---|
| CVE-2026-45813 | high | 8.8 | 1.10.0 | per vulnerability databases |
| CVE-2026-45811 | high | 7.5 | 1.10.0 | per vulnerability databases |
| CVE-2026-45815 | high | 7.5 | 1.10.0 | per vulnerability databases |
| CVE-2026-45816 | high | 7.5 | 1.10.0 | per vulnerability databases |
| CVE-2026-45812 | medium | 6.5 | 1.10.0 | per vulnerability databases |
| CVE-2026-46452 | medium | 5.3 | 1.10.0 | per vulnerability databases |
Which NimBLE version do I need to upgrade to?
Fixed in NimBLE 1.10.0: 6 CVEs of this version.
What changed against NimBLE 1.8.0?
4 CVEs of 1.8.0 are no longer listed for 1.9.0: CVE-2025-52435, CVE-2025-53470, CVE-2025-53477, CVE-2025-62235.
No CVE was added in 1.9.0.
What does the number mean for a device?
Counted are the CVEs public sources name for NimBLE version 1.9.0 (NVD). "Confirmed by the vendor" means the CVE record or advisory comes from the vendor itself and names this version as affected. Third-party records are counted but not marked as confirmed.
Whether a CVE is exploitable in a given device depends on which functions of the library the build contains and how they are configured. The list shows what is known for the version.
Questions
How many CVEs does NimBLE 1.9.0 have?
As of 13 Nov 2026, 6 CVEs are known for NimBLE 1.9.0, 0 critical and 4 high. From NimBLE 1.10.0 on, none of these CVEs is listed.
From which version are the CVEs of NimBLE 1.9.0 fixed?
From NimBLE 1.10.0 on, none of the 6 CVEs is listed. The "Fixed in" column names the fix version per CVE.
Sources
- [1]NVD