Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Arbitrary Code Execution in Adobe Connect Deserialization

IdentifiersCVE-2026-34615CWE-502· Deserialization of Untrusted Data

CVE-2026-34615 affects Adobe Connect versions 2025.3, 12.10, and earlier. The issue is a deserialization of untrusted data vulnerability (CWE-502). According to the provided content, processing attacker-controlled serialized data can lead to arbitrary code execution in the context of the current user. The record also notes changed scope. The supplied content is inconsistent on user interaction: one description states exploitation requires a victim to visit a maliciously crafted URL or interact with a compromised web page, while the mention context and extracted facts state exploitation does not require user interaction. Based on the explicit weakness classification and impact statement, this is best characterized as a network-reachable deserialization flaw in Adobe Connect that can execute attacker-controlled code with the privileges of the affected user context.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can provide arbitrary code execution in the context of the current user, enabling compromise of that user's session and actions available to that security context. The provided content also states an attacker could inject malicious scripts into a web page, potentially gaining elevated access or control over the victim's account or session. Because the record notes scope change and the included CVSS vector indicates high confidentiality and integrity impact, exploitation may allow access to sensitive data and unauthorized modification of application state or user-accessible resources. No availability impact is specifically indicated in the supplied content.

Mitigation

If you can’t patch tonight, do this now.

Until patches are applied, reduce exposure of Adobe Connect services to untrusted networks where possible, restrict access to trusted users and administrative paths, and monitor for suspicious requests targeting Connect instances. Because the supplied content is inconsistent regarding whether user interaction is required, defensive measures should cover both server-side exploitation attempts and client-side delivery via malicious URLs or compromised pages. Organizations should also harden browser and session security controls for Connect users and review logs for anomalous session activity. Specific vendor-recommended mitigations beyond patching are not available in the provided content.

Remediation

Patch, then assume compromise.

Upgrade Adobe Connect to a version newer than 2025.3 and 12.10, as the provided content states those versions and earlier are affected. Apply the vendor security update referenced by Adobe's advisory (APSB26-37). If precise fixed build numbers are needed, they are not provided in the supplied content and should be confirmed directly from the Adobe advisory.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdobeConnectapplication
AdobeConnect Desktop Applicationapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.