Please report suspected security vulnerabilities privately to the Apache Security Team at security@apache.org, following the ASF process at https://www.apache.org/security/. Do not open public GitHub issues or pull requests for security reports.

Apache NimBLE's security threat model — its scope, trust boundaries (the graduated radio-trust tiers), the security properties it does and does not provide, the adversary model, and a list of recurring non-findings — is documented in THREAT_MODEL.md.

Key point for triagers and scanners: a large part of BLE is unauthenticated by the Bluetooth specification (open advertising, traffic before encryption is established, and "Just Works" pairing, which provides no MITM protection). Those are spec-defined, not NimBLE bugs. The in-model surface is memory safety in the PDU parsers and the correctness of the Security Manager's cryptography. See THREAT_MODEL.md §9 and §11a.