CVE-2026-22844
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Command Injection vulnerability in Zoom Node Multimedia Routers (MMRs) before version 5.2.1716.0 may allow a meeting participant to conduct remote code execution of the MMR via network access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA command injection vulnerability in Zoom Node Multimedia Routers (MMRs) allows a meeting participant to execute arbitrary commands on the device via network access, potentially achieving full remote code execution. The vulnerability exists in versions prior to 5.2.1716.0 and stems from insufficient input validation allowing injected OS commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the device is a Zoom Node MMRCheck the device model number, firmware interface, or network banner for 'Zoom Node MMR' or 'Multimedia Router' designationAffected if The device is not a Zoom Node MMR product - this CVE does not apply
-
Check the installed firmware versionAccess the device administrative interface or check via SNMP/SSH: look for firmware version information in system status or device info pagesAffected if Firmware version is lower than 5.2.1716.0 (e.g., 5.2.1500.0, 5.1.x, etc.) - the device is likely vulnerable
-
Verify if network management interface is exposedCheck device network configuration for accessible HTTP/HTTPS or SSH interfaces exposed to network participantsAffected if The device management or participant interface is network-accessible from participant machines - required for the attack vector
-
Confirm meeting participant network access is enabledInspect meeting configuration settings to determine if participants can interact with the MMR network interface or send commandsAffected if Participants have direct network access to the MMR device - the vulnerability requires this access for command injection
The environment is affected if the device is a Zoom Node MMR running firmware version below 5.2.1716.0 with network-accessible participant interfaces enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Zoom Node MMR devices to firmware version 5.2.1716.0 or later. If immediate patching is not feasible, restrict network access to MMR devices and limit meeting participant privileges to reduce attack surface.
5.2.1716.0 or later
- Identify the Zoom Node MMR device(s) in your infrastructure that need remediation
- Locate the Zoom MMR administration interface or management console
- Check the current software version of each MMR device
- Download Zoom MMR software version 5.2.1716.0 or later from the official Zoom support portal
- Follow Zoom's standard upgrade procedure for Node MMR devices to apply the update
- After upgrading, verify that the MMR is running the patched version
- Confirm the vulnerability is resolved by ensuring the MMR version is 5.2.1716.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data