CVE-2025-53470VulnerabilityPublished 10 Jan 2026Updated 12 Jan 2026

CVE-2025-53470: Apache Mynewt NimBLE · Out-of-bounds Read

Affects Apache Mynewt NimBLESource CVE Database V5

Not known to be exploited · CVSS 3.1 Low : upgrade to 1.9 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.9

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade apache/mynewt-nimble to 1.9.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Mynewt NimBLE	Affected <=1.8	Fixed in–
GitHubapache/mynewt-nimble`pkg:github/apache/mynewt-nimble`Other threats	Affected <1.9	Fixed in 1.9

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-53470, European organizations should: 1) Upgrade all Apache NimBLE instances to version 1.9 or later, which contains the fix for this vulnerability. 2) Conduct an inventory of embedded and IoT devices using NimBLE to identify affected versions. 3) Implement strict Bluetooth controller validation and authentication mechanisms to prevent acceptance of malformed or malicious HCI events. 4) Employ network segmentation and access controls to limit Bluetooth communication to trusted devices only. 5) Monitor Bluetooth traffic for anomalous or malformed HCI events that could indicate exploitation attempts. 6) Collaborate with device manufacturers to ensure secure firmware updates and supply chain integrity. 7) Incorporate Bluetooth security best practices, including disabling unused Bluetooth interfaces and enforcing strong pairing methods. These steps go beyond generic patching by addressing the root cause and reducing the attack surface related to Bluetooth controller trust.

Description

Out-of-bounds Read vulnerability in Apache NimBLE HCI H4 driver. Specially crafted HCI event could lead to invalid memory read in H4 driver. This issue affects Apache NimBLE: through 1.8. This issue requires a broken or bogus Bluetooth controller and thus severity is considered low. Users are recommended to upgrade to version 1.9, which fixes the issue.

Impact

For European organizations, the impact of CVE-2025-53470 is generally low due to the limited severity and exploitation complexity. However, organizations deploying embedded systems or IoT devices that use Apache NimBLE for Bluetooth communication could face risks of information leakage or device instability if exposed to a malicious Bluetooth controller. This could be relevant in sectors such as manufacturing, healthcare, smart buildings, and critical infrastructure where Bluetooth-enabled embedded devices are prevalent. Although the vulnerability does not allow code execution or denial of service directly, any information disclosure or device malfunction could undermine operational security or reliability. The requirement for a broken or malicious Bluetooth controller limits remote exploitation, but insider threats or supply chain compromises could increase risk. European entities with extensive IoT deployments should evaluate their device firmware versions and Bluetooth controller security to mitigate potential exposure.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Jan 2026, 07:37 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats