Skip to content
major vulnerability· requires attention

Critical RCE in a widely used enterprise app (Adobe Connect); no user action required; could enable enterprise-wide compromise.

Web

CVE-2026-34615

9.3
Critical
EPSS 0.63%Patch availableApr 15, 2026

Adobe Connect deserialization leads to arbitrary code execution without user action.

common questions

Is CVE-2026-34615 being exploited?

Not confirmed. CVE-2026-34615 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.

How severe is CVE-2026-34615?

CVE-2026-34615 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-34615?

Yes. A fix has been recorded for CVE-2026-34615. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-34615 affect?

CVE-2026-34615 affects Adobe Connect 2025.3, 12.10 and earlier. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-34615?

Patch when available; isolate hosts; monitor logs for exploitation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Adobe Connect 2025.3, 12.10 and earlier
impact

Remote code execution in the current user context via crafted payload; no user interaction required.

action required

Immediate action required

affected versions
Adobe Adobe Connect
  • affected<= 12.10
vendor says fixed in12.11
Adobe Adobe Connect Desktop Application
  • affected<= 2025.3
vendor says fixed in2025.9

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free