Tom Dörr[verified]@tom_doerrPoC
The tweet shares a GitHub link to a research tool for CVE‑2025‑36911, indicating a PoC is likely available, but it provides no evidence of active exploitation, patches, or technical details.
Co11ateral[verified]@co11ateralDisclosure
The text announces CVE‑2025‑36911, outlining how Fast Pair can be abused to remotely activate microphones, but does not provide an exploit tool, active exploitation evidence, or a fix.
valeria lenoir[verified]@VLenoir13937Disclosure
CVE‑2025‑36911 targets Google Fast Pair, permitting unauthorised Bluetooth pairing and access to audio and microphone data, underscoring the attack surface of Bluetooth earbuds.
valeria lenoir[verified]@VLenoir13937PoC
The post announces a defensive tool repository for CVE-2025-36911, offering a PoC to verify Bluetooth headphone vulnerabilities and encouraging users to apply vendor patches.
Hermes Tool[verified]@Hermes_toollPoC
A GitHub repository is shared as a research tool for CVE-2025-36911, providing code that can act as a proof of concept but lacking exploit details, patch information, or evidence of current exploitation.
Sébastien Dudek 📡[verified]@FlUxIuSPoC
The post shares a GitHub link to an exploit repository for CVE-2025-36911, clearly indicating a proof of concept has been made available.
satoshi7[verified]@FredyBahenaMGeneral
The tweet merely cites the CVE number without any additional information about the vulnerability, exploitability, or mitigation.
valeria lenoir[verified]@VLenoir13937General
The post lists sources for CVE-2025-36911 and a step-by-step headphone check guide, but does not provide PoC, exploit, patch, or technical details.