Loading vulnerability…
Improper access control in Samsung Camera prior to version 16.5.00.28 allows local attacker to access location data. User interaction is required for triggering this vulnerability.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small 3-file repository containing a Python proof-of-concept simulation for CVE-2026-21014, plus a README and license. The only code file, can_replay_sim.py, is a minimal in-memory demonstration of a CAN bus replay attack: it defines send_can() and receive_can(), emits a simulated legitimate CAN frame with ID 0x100 and payload 01 00 00 00 (documented as a door unlock command), waits one second, retrieves the last observed frame, and retransmits it. There is no real CAN/socket interaction, no SocketCAN bindings, no ECU-specific logic, no packet capture from hardware, and no post-exploitation capability beyond replaying the stored frame. The README frames the attack as requiring physical access to the OBD-II port and explains the security weakness as lack of authentication/freshness in CAN. Overall, this is a benign proof-of-concept/demo of replay mechanics against automotive CAN messaging rather than a weaponized exploit.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this 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.