CVE-2025-52435
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-10

Last updated on: 2026-01-14

Assigner: Apache Software Foundation

Description
J2EE Misconfiguration: Data Transmission Without Encryption vulnerability in Apache NimBLE. Improper handling of Pause Encryption procedure on Link Layer results in a previously encrypted connection being left in un-encrypted state allowing an eavesdropper to observe the remainder of the exchange. This issue affects Apache NimBLE: through <= 1.8.0. Users are recommended to upgrade to version 1.9.0, which fixes the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-10
Last Modified
2026-01-14
Generated
2026-06-16
AI Q&A
2026-01-10
EPSS Evaluated
2026-06-15
NVD
CVE-2025-52435
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
apache nimble to 1.9.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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]

Impact Analysis

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]

Mitigation Strategies

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]

Compliance Impact

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]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-52435. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart