Command Injection RCE in Zoom Node Multimedia Routers
CVE-2026-22844 is a critical command injection vulnerability in Zoom Node Multimedia Routers (MMRs) affecting versions prior to 5.2.1716.0. The issue impacts the MMR module used in Zoom Node Meetings Hybrid (ZMH) and Zoom Node Meeting Connector (MC) deployments. According to Zoom, a meeting participant can exploit the flaw via network access to cause remote code execution on the MMR. The vulnerable component is the Multimedia Router responsible for processing meeting audio and video streams in these hybrid/connector environments. The published CVSS v3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, consistent with low attack complexity, low privileges, no user interaction, and high impact across confidentiality, integrity, and availability.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python proof-of-concept exploit (CVE-2026-22844.py) and a README describing the vulnerability and usage. The exploit targets Zoom Node MMR deployments prior to 5.2.1716.0 and performs unauthenticated network-based command injection leading to RCE. Core behavior: the script takes a target base URL and an arbitrary shell command, then iterates over four likely MMR control API paths. It sends an HTTPS POST with JSON body {action:"execute_control", control_command:"shell:<base64>", async:false}. The injected command is wrapped with START/END markers ("echo START; <cmd>; echo END") and base64-encoded to help bypass weak filtering. It treats HTTP 200/201/202/500 as potential success and attempts to extract command output between START/END from the response body. Notable targeting/assumptions: it sets X-Zoom-Meeting-ID (user-supplied or a fake default) and an Authorization: Bearer dummy-token header, implying the vulnerable endpoint may be reachable without strong authentication but may require meeting-context access. TLS verification is disabled (verify=False). The README provides example commands including reverse shell via bash /dev/tcp and file read of /etc/passwd. Overall purpose: operational PoC for remote command execution against exposed Zoom Node MMR control endpoints by exploiting insufficient sanitization of the control_command parameter.
Affected products & vendors
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.
Recent activity
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Zoom Node Multimedia Router (MMR) vulnerability that can allow a meeting participant to achieve remote code execution.
A critical command injection in Zoom Node Multimedia Routers (MMRs) enabling a meeting participant to achieve RCE over network access.
A critical command injection vulnerability in Zoom Node Multimedia Routers (MMRs) used in hybrid meeting environments that can allow arbitrary code execution by meeting participants; described as easy to exploit with high impact (CVSS 9.9).
Critical command injection in Zoom Node Multimedia Routers (Meeting Connector/Meetings Hybrid) enabling participant remote code execution on versions prior to 5.2.1716.0.
The version that knows your environment.
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.