Knowledge · Vulnerabilities by version

NimBLE 1.3.0: 15 known CVEs

15 CVEs, 0 of them critical and 0 actively exploited.

As of 13 Nov 2026, 15 CVEs are known for NimBLE 1.3.0, 0 critical and 9 high. The vendor names 2 in its own advisory for exactly this version. From NimBLE 1.10.0 on, none of these CVEs is listed.

Data queried 13 November 2026 · Page updated 13 November 2026 · 2 min read

At a glance
Version
NimBLE 1.3.0
Known CVEs
15
Critical / high
0 / 9
Actively exploited (CISA KEV)
0
Confirmed by the vendor
2

Checked on 13 Nov 2026

Which CVEs affect NimBLE 1.3.0?

No note: the vendor names the CVE in its own advisory for this version (2 of 15).

CVESeverityCVSSFixed fromNote
CVE-2026-45813high8.81.10.0per vulnerability databases
CVE-2025-62235high8.11.9.0per vulnerability databases
CVE-2024-24746high7.51.7.0
CVE-2024-51569high7.51.8.0
CVE-2025-52435high7.51.9.0per vulnerability databases
CVE-2025-53477high7.51.9.0per vulnerability databases
CVE-2026-45811high7.51.10.0per vulnerability databases
CVE-2026-45815high7.51.10.0per vulnerability databases
CVE-2026-45816high7.51.10.0per vulnerability databases
CVE-2026-45812medium6.51.10.0per vulnerability databases
CVE-2024-47248medium6.31.8.0per vulnerability databases
CVE-2026-46452medium5.31.10.0per vulnerability databases
CVE-2024-47249medium5.01.8.0per vulnerability databases
CVE-2024-47250medium5.01.8.0per vulnerability databases
CVE-2025-53470low3.11.9.0per vulnerability databases

Which NimBLE version do I need to upgrade to?

Fixed in NimBLE 1.7.0: 1 CVE of this version.

Fixed in NimBLE 1.8.0: 4 CVEs of this version.

Fixed in NimBLE 1.9.0: 4 CVEs of this version.

Fixed in NimBLE 1.10.0: 6 CVEs of this version.

What changed against NimBLE 1.2.0?

No CVE of 1.2.0 dropped out in 1.3.0.

No CVE was added in 1.3.0.

What does the number mean for a device?

Counted are the CVEs public sources name for NimBLE version 1.3.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.3.0 have?

As of 13 Nov 2026, 15 CVEs are known for NimBLE 1.3.0, 0 critical and 9 high. The vendor names 2 in its own advisory for exactly this version. From NimBLE 1.10.0 on, none of these CVEs is listed.

From which version are the CVEs of NimBLE 1.3.0 fixed?

From NimBLE 1.10.0 on, none of the 15 CVEs is listed. The "Fixed in" column names the fix version per CVE.

Sources

  1. [1]NVD

Which NimBLE version is in your build?

Vendor SDKs ship their own versions. Upload the AXF, HEX or firmware image: we read the versions from the binary and match the CVEs. Report and SBOM within three working days, free. The reports are in German.