CVE-2026-28623 Google CVE debrief

Who should care

Defenders responsible for managing and securing Android devices, especially those with local access to vulnerable devices, should assess exposure and prioritize patching. They should also review their systems for exposure, verify and apply patches from Google, and monitor for local attackers attempting to exploit this vulnerability.

Why it matters

CVE-2026-28623 is a local information disclosure vulnerability in Android that allows attackers to obtain Bluetooth MAC addresses without additional privileges. Defenders should prioritize patching and review systems for exposure.

• Local attackers may obtain Bluetooth MAC addresses, potentially aiding in further exploitation or tracking
• Defenders must verify and apply patches from Google to prevent exploitation
• Exposure requires local access, limiting but not eliminating the risk

Technical summary

The vulnerability exists in the BleRssiRangingCapabilities.java file, where a missing permission check allows local attackers to obtain the Bluetooth MAC address. This could lead to local information disclosure with no additional execution privileges needed. The vulnerability has a CVSS score of 3.3 and a severity of LOW. The CVE record and NVD entry provide additional details on the vulnerability, including its description and affected versions. However, specific version remediation details are not provided in the corpus.

Defensive priority

Defenders should prioritize verifying and applying patches from the vendor, Google, for affected Android versions. They should also review their systems for exposure, especially those with local access to vulnerable devices.

Recommended defensive actions

• Verify and apply patches from Google for affected Android versions
• Review systems for exposure, especially those with local access to vulnerable devices
• Monitor for local attackers attempting to exploit this vulnerability
• 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
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, specific version remediation details are not provided in the corpus.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.