# CVE-2025-20329: Cisco TelePresence Collaboration Endpoint and RoomOS Software Information Disclosure Vulnerability

> An authenticated admin can view sensitive credentials in clear text logs when SIP media logging is enabled, potentially exposing PII.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-rvvf-ghr3-j46w

## What is CVE-2025-20329?

CVE-2025-20329 is a medium-severity vulnerability in Cisco RoomOS Software, published on 15 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the logging component of Cisco TelePresence Collaboration Endpoint (CE) and Cisco RoomOS Software could allow an authenticated, remote attacker to view sensitive information in clear text on an affected system. To exploit this vulnerability, the attacker must have valid administrative credentials.

This vulnerability exists because certain unencrypted credentials are stored when SIP media component logging is enabled. An attacker could exploit this vulnerability by accessing the audit logs on an affected system and obtaining credentials to which they may not normally have access. A successful exploit could allow the attacker to use those credentials to access confidential information, some of which may contain personally identifiable information (PII).
Note: To access the logs that are stored in the Webex Cloud or stored on the device itself, an attacker must have valid administrative credentials.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-20329?

It affects 2 products.


Products: Cisco Roomos, Cisco Telepresence Collaboration Endpoint.

## How do I fix CVE-2025-20329?

No fix has been published for CVE-2025-20329 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20329 being exploited?

There is no known exploitation of CVE-2025-20329 in the wild and no public exploit code.

## Other vulnerabilities in Cisco RoomOS Software

- [CVE-2026-20150](https://insights.sbomify.com/CVE-2026-20150/): Cisco RoomOS Security Hardening Release - Access Control Vulnerabilities (high 8.8)
- [CVE-2019-15288](https://insights.sbomify.com/CVE-2019-15288/): Cisco TelePresence Collaboration Endpoint, TelePresence Codec, and RoomOS Software Privilege Escalation Vulnerability (high 8.8)
- [CVE-2026-20156](https://insights.sbomify.com/CVE-2026-20156/): Cisco RoomOS Security Hardening Release - Buffer Management Vulnerabilities (high 8.1)
- [CVE-2026-20153](https://insights.sbomify.com/CVE-2026-20153/): Cisco RoomOS Security Hardening Release - Input Validation Vulnerabilities (high 7.5)
- [CVE-2026-20157](https://insights.sbomify.com/CVE-2026-20157/): Cisco RoomOS Security Hardening Release - Missing Encryption Vulnerabilities (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20329 and fix it if it is affected.

What it is: CVE-2025-20329 is a medium-severity vulnerability in Cisco RoomOS Software, published on 15 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20329 in the wild and no public exploit code.

Affected product: Cisco RoomOS Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20329/ (Markdown: https://insights.sbomify.com/CVE-2025-20329/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20329
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20329
- OSV: https://osv.dev/vulnerability/CVE-2025-20329

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20329/
Summaries are generated and may contain mistakes; the official description above is the record.