# CVE-2026-76435: Cisco Expressway Series Information Disclosure Vulnerability


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-667p-34p2-c6m9

## What is CVE-2026-76435?

CVE-2026-76435 is a medium-severity vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 21 Oct 2026. 

### Official description

A vulnerability in Cisco Expressway Series could allow an unauthenticated, remote attacker to obtain sensitive information from an affected device.

This vulnerability is due to insufficient authorization checks of HTTP requests during Mobile and Remote Access (MRA) provisioning. An attacker could exploit this vulnerability by submitting a crafted URL request to an affected device. A successful exploit could allow the attacker to access sensitive information that they would otherwise not have authorization to access.
Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-76435?


## How do I fix CVE-2026-76435?

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

## Is CVE-2026-76435 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76435 and fix it if it is affected.

What it is: CVE-2026-76435 is a medium-severity vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76435 in the wild and no public exploit code.

Affected product: Cisco TelePresence Video Communication Server (VCS) Expressway. 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-2026-76435/ (Markdown: https://insights.sbomify.com/CVE-2026-76435/index.md)
```

## Sources

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

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