Introduction
A path traversal flaw in Adobe Connect on Windows lets a low-privileged, authenticated user reach files outside the directory the application intended to expose, over the network and without any user interaction. Adobe's bulletin scores it CVSS 9.9 and labels its impact as arbitrary code execution, which makes this one of the more consequential issues in the November 2026 Adobe Connect update.
Adobe Connect is Adobe's platform for meetings, webinars, and virtual classrooms, which Adobe markets as a purpose-built virtual learning environment for complex training. It can be deployed as a hosted service, as a managed service, or on premises, and the location of the Adobe Connect Server varies by option. The reviewed sources include no independent market-share figures. This bulletin targets on-premises Windows server deployments, which customer organizations operate directly.
Technical information
Root cause
CVE-2026-121906 is classified as CWE 22, Improper Limitation of a Pathname to a Restricted Directory. According to the patch information, a user-supplied path component was not limited to the directory it was meant to stay in. As a result, a low-privileged authenticated user could cause the server to access files outside that directory over the network.
The CVE record describes the outcome as arbitrary file system read, meaning access to sensitive files and directories outside the intended access scope. It also states that exploitation does not require user interaction and that scope is changed.
Scoring and the impact discrepancy
Adobe and the CVE record both assign a CVSS 3.1 score of 9.9 with this vector:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Broken down:
- AV:N: reachable over the network
- AC:L: low attack complexity
- PR:L: low privileges required, so this is not described as an unauthenticated issue
- UI:N: no user interaction required
- S:C: scope changed
- C:H/I:H/A:H: high impact to confidentiality, integrity, and availability
The sources describe the impact differently. The NVD/CVE description, which the GitHub advisory reuses, says arbitrary file system read. Adobe's bulletin table rates the issue Critical with the impact "Arbitrary code execution." None of the published material explains how a read primitive relates to code execution, and the high integrity and availability ratings in the vector fit the broader vendor rating better than a pure read. Our view is that defenders should prioritize based on the more severe vendor classification, without treating any specific escalation chain as established fact.
Attack flow
Based on what the sources state, the exploitation conditions look like this:
- The attacker holds a low-privileged account on an affected Adobe Connect server running on Windows.
- The attacker sends a network request in which a path component they control is not restricted to the intended base directory.
- The server resolves that path outside the restricted directory and returns or operates on files beyond the intended access scope, with no action needed from any other user.
Adobe has not disclosed the vulnerable endpoint, code path, request format, the precise account type required, or which files are reachable. Adobe Connect is closed source, so there is no public diff to analyze. Fixes for this bug class usually canonicalize the requested path, then confirm that the resolved path stays inside an allow-listed base directory before opening the file. This is an inference from the general pattern and cannot be confirmed for this CVE.
Patch information
Adobe fixed CVE-2026-121906 in security bulletin APSB26 191, published November 10, 2026 with Priority 2. The vendor update is the only fix, and it ships as maintenance builds for each supported release line. Move to the fixed build for the branch you already run:
- 12.8 (12.8 and earlier): fixed in 12.8.a
- 12.9 (12.9 and earlier): fixed in 12.9.a
- 12.10 (12.10 and earlier): fixed in 12.10.f
- 12.11 (12.11 and earlier): fixed in 12.11.i
- 12.12 (12.12 and earlier): fixed in 12.12.a
The letter suffixes indicate Adobe backported the fix into each branch. A 12.10 deployment, for example, can patch in place to 12.10.f without first moving to 12.12. Adobe's general guidance is still to update to the newest version, and it points administrators to its on-premises installation instructions and release notes for upgrade steps. The bulletin provides no workaround.
The update bundles fixes for 23 other CVEs, and several are in the same family. CVE-2026-121351, CVE-2026-121354, and CVE-2026-121349 are also path traversals, and CVE-2026-121887 and CVE-2026-121890 are XML external entity (XXE) bugs that also lead to file access. You cannot deploy a fix for CVE-2026-121906 in isolation. Installing the fixed build closes all of these together.
Adobe credits Jim Green with reporting the vulnerability. The GitHub advisory for this CVE is unreviewed, lists no affected packages, and points only to NVD and Adobe's bulletin.
Affected systems and versions
- Adobe's bulletin: Adobe Connect 12.12 and earlier on Windows.
- Per release line (CNA record): 12.8 and earlier, 12.9 and earlier, 12.10 and earlier, 12.11 and earlier, and 12.12 and earlier, with unaffected builds 12.8.a, 12.9.a, 12.10.f, 12.11.i, and 12.12.a respectively.
The CVE record also expresses an affected range of version 0 through 12.8, with 12.8.a unaffected. On its face, that does not match Adobe's "12.12 and earlier" statement, and the record does not explain its version notation. For remediation decisions, rely on Adobe's bulletin and its branch-specific fixed builds rather than trying to infer coverage from the CVE record alone.
The affected platform is Windows. Adobe Connect is also offered as hosted and managed service deployments, but the bulletin specifically scopes the affected product to Windows installations.
Vendor security history
Adobe's Product Security Incident Response Team manages its vulnerability disclosure program and provides a reporting process for customers, partners, penetration testers, and researchers. Adobe Connect has had several security bulletins in 2026:
- A May bulletin addressed critical vulnerabilities that could lead to arbitrary code execution and privilege escalation.
- A September bulletin addressed critical and important issues with impacts including arbitrary code execution and file system read. Adobe stated it was not aware of in-the-wild exploitation for those issues.
- The November bulletin, APSB26 191, addresses this CVE along with 23 others.
For APSB26 191, Adobe likewise states it is not aware of any in-the-wild exploits, and the CVE record supplies no exploit evidence or threat-actor attribution. That statement reflects what Adobe is aware of. It is not proof that exploitation has not occurred. File-read and path-handling issues have recurred across this year's bulletins, though the sources do not support broader conclusions about Adobe's overall security posture relative to other vendors.
References
- NVD: CVE-2026-121906
- CVE Record: CVE-2026-121906
- Adobe Security Bulletin APSB26 191: Security update available for Adobe Connect
- GitHub Advisory for CVE-2026-121906
- SmartScope: Adobe Connect Windows multiple critical vulnerabilities (APSB26 191)
- CVE Brief: CVE-2026-121906
- securityvulnerability.io: Path Traversal Vulnerability in Adobe Connect
- Adobe Product Security Incident Response Team
- Adobe Connect for training and webinars
- Adobe Connect Security Overview (PDF)
- Adobe Security Bulletin APSB26 150
- Adobe Security Bulletin APSB26 50
- Adobe Security Bulletin APSB26 182



