CVE-2025-52435
BaseFortify
Publication date: 2026-01-10
Last updated on: 2026-01-14
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | nimble | to 1.9.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-5 | Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-52435 is a vulnerability in Apache NimBLE (up to version 1.8.0) where improper handling of the Pause Encryption procedure at the Link Layer causes a previously encrypted Bluetooth connection to revert to an unencrypted state. This allows an eavesdropper to observe the remainder of the data exchange. The issue arises because the system does not correctly enforce encryption state checks on received control messages, allowing data transmission without encryption. The vulnerability is fixed in version 1.9.0 by enforcing strict validation of control messages based on the encryption state and properly handling encryption pause and resume procedures. [2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can impact you by exposing sensitive data transmitted over Bluetooth connections to eavesdropping. Since the connection can revert from encrypted to unencrypted without proper handling, an attacker within range could intercept and observe confidential information that was expected to be protected by encryption. This compromises the confidentiality and security of Bluetooth communications using affected versions of Apache NimBLE. [3]
What immediate steps should I take to mitigate this vulnerability?
Users are recommended to upgrade Apache NimBLE to version 1.9.0, which contains fixes for this vulnerability. The patches enforce strict validation of Link Layer Control PDUs based on encryption state and ensure proper termination of connections when encryption cannot be resumed, preventing unencrypted data transmission. Therefore, immediate mitigation involves upgrading to Apache NimBLE 1.9.0 or later. [2, 3, 4]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows a previously encrypted Bluetooth connection to revert to an unencrypted state, enabling eavesdroppers to observe data transmissions. Such exposure of sensitive data without encryption can lead to non-compliance with data protection standards and regulations like GDPR and HIPAA, which require protection of personal and health information during transmission. Therefore, the vulnerability poses a risk to compliance by potentially allowing unauthorized data disclosure. [3, 4]