BLUFFS (Bluetooth Forward and Future Secrecy Attacks and Defenses) is an architectural weakness affecting Bluetooth BR/EDR devices implementing Secure Simple Pairing and Secure Connections under Bluetooth Core Specification versions 4.2 through 5.4. A man-in-the-middle attacker can interfere with encryption-procedure initiation to force negotiation of a reduced encryption-key length. The resulting short key may be feasible to recover, enabling compromise of the confidentiality and integrity of the Bluetooth link.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Bluetooth architectural weakness composed of six attacks that can force weak session keys, enabling man-in-the-middle attacks, impersonation, and possible decryption of past and future sessions.
Bluetooth vulnerability affecting forward and future secrecy protections.
Linux kernel Bluetooth vulnerability involving forward and future secrecy attacks.
Linux kernel Bluetooth forward- and future-secrecy vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.