Loading vulnerability…
Securly Chrome Extension version 3.0.7 downloads config.json over HTTP and compiles server-provided pattern strings into JavaScript regular expressions using new RegExp() without validating regex complexity. Because the configuration is retrieved over an unauthenticated and unencrypted channel, an on-path attacker can tamper with the response and inject crafted regular expression patterns designed to trigger catastrophic backtracking during evaluation. This creates a regular expression denial of service condition in the extension that can affect browsing activity broadly.
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 repository is a small Python proof-of-concept demonstrating an unsigned printer firmware update vulnerability tracked as CVE-2026-8888. It contains two executable scripts: malicious_update_server.py, which starts a simple HTTP server on 0.0.0.0:80 and returns a static attacker-controlled firmware blob, and printer_firmware_server.py, which simulates a vulnerable printer by downloading firmware from http://updates.printer.local/firmware.bin and saving it to /tmp/firmware.bin without any signature verification. The exploit capability is straightforward: if an attacker can redirect the victim printer's update request via DNS spoofing, host manipulation, or MITM, they can supply arbitrary firmware. The code does not include a real post-exploitation implant; the payload is a placeholder string, so this is best characterized as an operational PoC rather than a weaponized exploit. Repository structure is minimal: LICENSE, README.md with vulnerability description and usage steps, and the two Python scripts implementing the attacker server and vulnerable client simulation.
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.
3 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.