CVE-2026-21015 is an incorrect default permissions vulnerability in Samsung FactoryCamera prior to the SMR May-2026 Release 1. The flaw allows a local attacker to access a unique identifier due to overly permissive default access controls on the affected component.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This is a small proof-of-concept repository demonstrating a PHP filter-chain arbitrary file read / LFI scenario labeled as CVE-2026-21015. The repository contains two code files: vulnerable.php, which implements the vulnerable behavior, and exploit_php_filter.py, which performs the attack. The PHP script takes a user-controlled page parameter and passes it directly into include("php://filter/convert.base64-encode/resource=" . $file), allowing an attacker to supply traversal sequences and cause arbitrary local files to be included through the php://filter wrapper. Because the wrapper base64-encodes the file contents, the Python exploit simply sends a GET request to the vulnerable endpoint with page=../../../etc/passwd, then base64-decodes the response and prints the recovered file contents. The exploit has a single capability: arbitrary local file read / source disclosure from the web server context. It does not provide code execution, persistence, or post-exploitation features. Repository structure is minimal: LICENSE, README.md with usage notes, exploit_php_filter.py as the client PoC, and vulnerable.php as the intentionally insecure target example.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.