CVE-2026-45813 Apache Software Foundation CVE debrief

Who should care

Users of Apache NimBLE versions prior to 1.10.0 should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to version 1.10.0 or applying the available patches. Operators, administrators, and security teams responsible for Apache NimBLE deployments should review the vulnerability details and take necessary actions to protect their systems.

Technical summary

The vulnerability is caused by improper validation when parsing BASS service 'Add Source' and 'Modify Source' operation PDU, which could result in a stack buffer overflow or arbitrary out-of-bound read. This issue has a CVSS score of 8.8 and is classified as HIGH severity. The vulnerability affects Apache NimBLE through version 1.9.0 and is fixed in version 1.10.0. Users should upgrade to version 1.10.0 or apply the available patches to mitigate this vulnerability.

Defensive priority

High priority should be given to upgrading to version 1.10.0 or applying the available patches to mitigate this vulnerability. Additionally, restricting access to the BASS service to trusted devices and monitoring for suspicious activity on Bluetooth connections can help reduce the risk of exploitation.

Recommended defensive actions

• Upgrade to Apache NimBLE version 1.10.0 or later
• Apply patches provided by the vendor
• Restrict access to the BASS service to trusted devices
• Monitor for suspicious activity on Bluetooth connections
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-24T13:18:24.087Z and was last modified on 2026-07-27T14:41:12.090Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus and may not reflect the full scope of the vulnerability. Users should verify the details with the official CVE record and NVD entry for the most accurate and up-to-date information.

Official resources