Skip to main content
VulnerabilityPublished Updated

CVE-2025-27203: Adobe Connect · Deserialization of Untrusted Data

Affects Adobe ConnectSource CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Adobe Adobe ConnectAffected
  • =0
Fixed in–

AI-suggested

Until official patches are released by Adobe, organizations should implement several specific mitigations to reduce risk: 1) Educate users about the dangers of opening unsolicited links or files related to Adobe Connect sessions to minimize user interaction exploitation vectors. 2) Restrict and monitor network traffic to Adobe Connect servers, employing application-layer firewalls and intrusion detection/prevention systems to detect anomalous deserialization attempts or unusual payloads. 3) Apply strict input validation and sandboxing where possible to isolate Adobe Connect processes and limit the impact of potential code execution. 4) Use endpoint detection and response (EDR) tools to monitor for suspicious behaviors indicative of exploitation, such as unexpected process spawning or memory manipulation. 5) Segment Adobe Connect servers from critical infrastructure to contain potential breaches. 6) Regularly review and update incident response plans to include scenarios involving deserialization vulnerabilities. 7) Stay informed through Adobe security advisories and apply patches immediately upon availability. These targeted actions go beyond generic advice by focusing on user behavior, network controls, and proactive monitoring specific to the nature of this vulnerability.

Description

Adobe Connect versions 24.0 and earlier are affected by a Deserialization of Untrusted Data vulnerability that could lead to arbitrary code execution by an attacker. Exploitation of this issue does require user interaction and scope is changed.

References

Community reviews

Loading reviews…