CVE-2025-34093 is an authenticated command injection vulnerability in the Polycom HDX Series command shell interface accessible via Telnet. The vulnerability resides in the 'lan traceroute' command within the devcmds console, which fails to properly sanitize user-supplied input. This allows an attacker with Telnet access (either via known credentials or unauthenticated access if enabled) to inject shell metacharacters and execute arbitrary system commands as root.
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 contains a single Metasploit module: 'polycom_hdx_traceroute_exec.rb', which exploits a command execution vulnerability (CVE-2025-34093) in Polycom HDX Series devices. The exploit targets the device's command shell, accessible via Telnet (default port 23), and abuses the 'lan traceroute' developer command to execute arbitrary shell commands. The module supports both authenticated and unauthenticated access, depending on device configuration. Upon successful exploitation, it stages a payload (default: reverse shell) using openssl s_client to connect back to an attacker-controlled listener. The code is written in Ruby and follows standard Metasploit module structure, with options for specifying target address, port, authentication password, and callback host/port. The exploit is weaponized, allowing for customizable payloads and automated exploitation within the Metasploit framework.
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.