Loading vulnerability…
JUNG Smart Visu Server version 1.1.1050 contains a denial of service vulnerability that permits an unauthenticated remote attacker to trigger a server shutdown or reboot. According to the provided content, exploitation requires only a single crafted POST request and does not require authentication. The issue appears to stem from exposure of a reboot/shutdown-capable server function or endpoint without proper authentication controls, allowing remote invocation of administrative power-management actions.
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 (1 hidden).
Repository contains a single Python PoC exploit (CVE-2026-26235.py) and a README. The exploit targets JUNG Smart Visu Server <= 1.1.1050 and abuses missing authentication (CWE-306) on exposed CGI management scripts. It constructs a target URL by appending either /cgi-bin/reboot.sh or /cgi-bin/shutdown.sh to a user-supplied base URL and sends an unauthenticated HTTP POST (empty body) using the requests library. The script supports selecting the action (reboot/shutdown), configuring timeout, and toggling TLS certificate verification (urllib3 warnings disabled). Success is inferred from HTTP 200/30x responses or from subsequent timeout/connection errors (which may indicate the device went down). Overall purpose: demonstrate unauthenticated remote reboot/shutdown leading to denial of service via network-accessible web interface endpoints.
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.
7 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.