Skip to content
major vulnerability· requires attention

Affects Adobe Connect, widely used enterprise app; critical XSS in web interface could enable session hijacking/credential theft.

Web

CVE-2026-27246

9.3
Critical
EPSS 0.30%Patch availableApr 15, 2026

DOM-based XSS in Adobe Connect can run malicious JS from crafted pages.

common questions

Is CVE-2026-27246 being exploited?

Not confirmed. CVE-2026-27246 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.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-27246?

CVE-2026-27246 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-27246?

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

What does CVE-2026-27246 affect?

CVE-2026-27246 affects Adobe Connect 2025.3, Adobe Connect 12.10, Earlier versions of Adobe Connect. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-27246?

Patch when available; if not, limit access and monitor for abuse.

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

executive summary
technical analysis
affected
Adobe Connect 2025.3Adobe Connect 12.10Earlier versions of Adobe Connect
impact

Attacker can execute JavaScript in victim's browser via a crafted Adobe Connect page, potentially stealing session cookies or credentials.

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