vulns.cofield index
Enter
Search
LanguageEN
EnglishCurrentEspañolSame sectionPortuguês (Brasil)Same sectionFrançaisSame sectionDeutschSame section日本語Same section简体中文Same section
Learning
Browse all pagesCurrent: Intelligence
Known vulnerability record

CVE-2026-20230

Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) Vulnerability

Stable IDcve:CVE-2026-20230Source record dateHuman reviewNot recordedProvenanceSource-linked CVE, KEV, and EPSS signals
Summary

Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) Vulnerability

Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) contain a server-side request forgery (SSRF) Vulnerability that could allow an unauthenticated, remote attacker to write files to the underlying operating system that could be used later to elevate to root.

Vulns.co field classification

Identity boundary on enterprise application

Derived analysis: these labels are inferred from the source title, product, and summary. They are not vendor, CVE, CISA, or FIRST classifications.

Failure classIdentity boundary
Product laneEnterprise application
Attention stateKnown exploited, ransomware use unknown
Hunter pivot

Diagram the identity state machine. Compare two controlled identities across alternate routes, token audiences, role changes, recovery flows, and session rotation. Change one property per request.

Signals

Keep the signals separate

CVSS severityhighScore 8.6 · source cisco
EPSS probability88.2%Probability of exploitation in the next 30 days; not severity
CISA KEVKnown exploitedAdded 2026-06-25
Ransomware useunknownPreserved as known / unknown, not a truthy default
Research boundary

Confirm the product before the behavior.

  1. Match the exact product, build, deployment mode, and exposed component.
  2. Read the vendor advisory and current program policy.
  3. Choose one non-destructive discriminator with an explicit negative control.
  4. Stop at the first sufficient proof. A CVE match is context, not permission.
Timeline

Dates and provenance

CVE published
2026-06-03
CVE modified
2026-07-01
KEV date added
2026-06-25
Dataset fetched
2026-08-25T13:17:16.734Z
Sources

Original records

Version history: normalized permanent page created 2026-08-20. Machine-enriched fields remain source-attributed.