Skip to main content
VulnerabilityPublished Updated

CVE-2025-53477: Apache Mynewt NimBLE · NULL Pointer Dereference

Affects Apache Mynewt NimBLESource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 1.9.0 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.9.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade apache/mynewt-nimble to 1.9.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Mynewt NimBLEAffected
  • <=1.8.0
Fixed in–
GitHubapache/mynewt-nimblepkg:github/apache/mynewt-nimbleOther threatsAffected
  • <1.9.0
Fixed in
  • 1.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-53477, European organizations should: 1) Upgrade all Apache NimBLE instances to version 1.9.0 or later, where the vulnerability is fixed. 2) Implement strict supply chain controls to ensure Bluetooth controllers are authentic and uncompromised, reducing the risk of malicious or faulty devices triggering the flaw. 3) Enable asserts during development and testing phases to detect abnormal behavior early. 4) Monitor BLE device logs and system stability for signs of crashes or unexpected resets that could indicate exploitation attempts. 5) Employ network segmentation and access controls to limit exposure of BLE devices to untrusted networks or actors. 6) Conduct regular firmware and software audits on BLE-enabled devices to ensure timely application of security patches. 7) Educate technical staff on the specific risks associated with BLE stack vulnerabilities and the importance of maintaining updated software. These targeted actions go beyond generic advice by focusing on the unique exploitation conditions and operational context of Apache NimBLE deployments.

Description

NULL Pointer Dereference vulnerability in Apache Nimble. Missing validation of HCI connection complete or HCI command TX buffer could lead to NULL pointer dereference. This issue requires disabled asserts and broken or bogus Bluetooth controller and thus severity is considered low. This issue affects Apache NimBLE: through 1.8.0. Users are recommended to upgrade to version 1.9.0, which fixes the issue.

References

Community reviews

Loading reviews…