dbcve.org
RoomosOperating system · Cisco

CVE-2026-20157

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 11.32.6.0 / 11.39.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco RoomOS engineering team has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-20157 are related to missing encryption that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-311.

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 · moderate confidence

Cisco RoomOS contains multiple vulnerabilities related to missing encryption (CWE-311). The internal security review identified that sensitive data is not properly encrypted, allowing potential interception or exposure. With a CVSS of 7.5, this is a high-severity network-exploitable issue likely impacting confidentiality of data in transit or at rest.

MitigationApply the Cisco RoomOS software hardening update released as part of this security review. Organizations should obtain the patch from Cisco's official channels and update affected RoomOS deployments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RoomosOperating system
Affected:< 11.32.6.0>= 26.0.1.2, < 26.5.2.2
Roomos CloudOperating system
Affected:< 11.39.1.1>= 26.0.1.2, < 26.7.1.7

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco RoomOS deployment
    Identify the device and verify it runs Cisco RoomOS firmware. Access the device web interface or CLI and retrieve the device type and operating system information.
    Affected if Device is not running Cisco RoomOS - this CVE is specific to RoomOS.
  2. Check RoomOS software version
    Access the RoomOS admin web interface or CLI and locate the software version. In the web UI, go to System Information or use the CLI command 'show version' to retrieve the exact RoomOS build version.
    Affected if Version matches the vulnerable range listed in Cisco's advisory for this CVE; compare your installed version to the affected versions.
  3. Verify encryption configuration for sensitive data
    Access RoomOS security settings in the admin interface. Check encryption-related configuration options for data at rest (local storage encryption) and data in transit (TLS, SRTP, or other transport security settings).
    Affected if Encryption for sensitive data is disabled, not configured, or uses weak/obsolete encryption protocols - the missing encryption flaw applies.
  4. Inspect data transmission for plaintext sensitive content
    Use network capture tools to capture traffic from the RoomOS device. Analyze the captured packets to determine if sensitive data (credentials, call metadata, configuration details) is transmitted without encryption.
    Affected if Sensitive data is observed being transmitted in plaintext or with insufficient encryption - confirming the vulnerability is present and exploitable.

A user is affected if the device runs a vulnerable Cisco RoomOS version AND has encryption disabled or misconfigured for sensitive data handling, allowing potential interception or exposure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 11.32.6.0 / 11.39.1.1 / 26.5.2.2 or later
Fixed in 11.32.6.011.39.1.126.5.2.2
Interim mitigation

Apply the Cisco RoomOS software hardening update released as part of this security review. Organizations should obtain the patch from Cisco's official channels and update affected RoomOS deployments.

Fix this in Roomos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20157 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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