dbcve.org
ConnectApplication · Adobe

CVE-2026-34617

HIGH · 8.7 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 12.11 / 2025.9.15 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Connect versions 2025.3, 12.10 and earlier are affected by a Cross-Site Scripting (XSS) vulnerability that could result in privilege escalation. A low-privileged attacker could exploit this vulnerability to inject malicious scripts into a web page, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Adobe Connect versions 2025.3 and earlier contain a stored or reflected Cross-Site Scripting (XSS) vulnerability that allows low-privileged authenticated users to inject malicious JavaScript into web pages. Due to scope change, this injected script can potentially access resources or functionality outside the vulnerable component, enabling privilege escalation to higher-tier accounts or session hijacking. Exploitation requires tricking victims into visiting crafted URLs or interacting with compromised interface elements.

MitigationApply the vendor patch when available; until then, implement output encoding and input validation on user-supplied data, configure Content-Security-Policy headers to restrict script execution, and educate users about avoiding suspicious URLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ConnectApplication
Affected:< 12.11
Connect Desktop ApplicationApplication
Affected:<= 2025.3< 2025.9.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Connect web application version
    Log into the Adobe Connect management console or check the version displayed in the application. Alternatively, check the installer or About dialog within the Adobe Connect interface.
    Affected if The installed version is less than 12.11 or falls within 2025.3 and earlier
  2. Check Adobe Connect Desktop Application version
    Open the Adobe Connect Desktop Application and navigate to Help > About, or right-click the application icon and select About. The version number is typically displayed in the format YYYY.X.
    Affected if The installed version is 2025.3 or earlier, or less than 2025.9.15
  3. Identify if web-facing access is enabled
    Determine if the Adobe Connect web interface is accessible externally or to low-privileged users. Review network firewall rules and Adobe Connect user permission settings.
    Affected if The web interface is accessible to unauthenticated or low-privileged users, allowing them to receive specially crafted URLs
  4. Review URL parameter handling
    Inspect web traffic and application logs for unusual URL parameters being passed to Adobe Connect endpoints. Use browser developer tools to examine how user-supplied parameters are reflected in responses.
    Affected if User-supplied URL parameters are reflected in server responses without proper encoding, indicating the vulnerable code path exists

A user is affected if they are running Adobe Connect versions below 12.11 or Adobe Connect Desktop Application at or below 2025.3 (or below 2025.9.15), and the web interface is accessible to low-privileged users who could be targeted with malicious crafted URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.11 / 2025.9.15 or later
Fixed in 12.112025.9.15
Interim mitigation

Apply the vendor patch when available; until then, implement output encoding and input validation on user-supplied data, configure Content-Security-Policy headers to restrict script execution, and educate users about avoiding suspicious URLs.

Recommended fix High confidence

Adobe Connect 12.11 or later; Connect Desktop Application 2025.9.15 or later

  1. Identify which Adobe Connect product is in use: Adobe Connect (server/web interface) or Connect Desktop Application
  2. For Adobe Connect (server/web): upgrade to version 12.11 or later
  3. For Connect Desktop Application: upgrade to version 2025.9.15 or later
  4. After upgrade, clear browser caches and sessions to avoid stale script caching
  5. Verify the installed version matches the fixed release to confirm remediation
Caveat Standard upgrade considerations apply - review Adobe's release notes for any deprecated features or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34617 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data