Introduction
A path traversal flaw in Adobe Connect lets an attacker holding nothing more than a low-privileged account reach outside a restricted directory over the network, with no user interaction. Adobe and the CVE record rate the result as critical, with a CVSS 3.1 score of 9.6. Because Connect is a training and webinar platform that admits external attendees by design, the "low privileges required" condition in CVE-2026-121349 is a thin barrier for many self-managed deployments.
The CVE record describes the impact as arbitrary code execution in the context of the current user, plus elevated access or control over the victim's account or session. Adobe's bulletin, APSB26-191, categorizes the same issue as privilege escalation. Adobe says it is not aware of exploits in the wild, and the CVE is not listed in the CISA KEV catalog as of November 11, 2026.
Technical information
Root cause
CVE-2026-121349 is classified as CWE-22, Improper Limitation of a Pathname to a Restricted Directory. In this class of bug, the application builds a file system path from attacker-influenced input without constraining the resolved path to the directory it is supposed to stay in, so traversal sequences such as ../ (or encoded forms of them) let a request reach files elsewhere on the host.
Adobe Connect is closed source and Adobe has published no technical details. The CVE record does not identify a vulnerable URL, request field, file path, exploit chain, or proof of concept, so the specific vulnerable component cannot be confirmed from the available sources. We have no vulnerable code to show, and we are not going to guess at it.
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- AV:N / AC:L: reachable over the network with low attack complexity.
- PR:L: the attacker needs only a low-privileged account.
- UI:N: no victim action is required.
- S:C: scope is changed, meaning the scored impact reaches beyond the vulnerable component itself.
- C:H / I:H / A:N: high confidentiality and integrity impact, no availability impact.
The NVD and CVE description calls the impact arbitrary code execution in the context of the current user, while Adobe's bulletin calls it privilege escalation. Both sources agree on the 9.6 score and critical severity.
Likely attack flow
The following flow is assembled from the CVE description, the CVSS vector, the CAPEC patterns OffSeq associates with this CWE, and ThreatAft's independent guidance. The exact endpoint and parameter remain unknown.
- The attacker authenticates with a low-privileged account. On a platform built for webinars with external attendees, this may not require compromising anyone.
- The attacker sends a network request in which a path value contains traversal sequences. OffSeq maps the flaw to plain path traversal (CAPEC-126), combined slash and URL encoding (CAPEC-64), web input passed to file system calls (CAPEC-76), and escaped or alternately encoded slashes (CAPEC-78/79). Together these describe the input variants an attacker would try.
- The server resolves the path outside its intended base directory. ThreatAft's hunting guidance for this bulletin's path traversal flaws centres on the Connect web process reading configuration files or credential stores outside the web root.
- The attacker escalates. Per the CVE record, the outcome is elevated access or control over the victim's account or session, or code execution in the context of the current user. Because scope is changed, the impact is not confined to the vulnerable component.
ThreatAft also notes that the path traversal and SSRF flaws in APSB26-191 are more useful to an attacker when the Connect admin interface is reachable from the same network segment as the meeting service.
Patch information
Adobe fixed CVE-2026-121349 in security bulletin APSB26-191, published November 10, 2026, with a vendor priority rating of 2. Because Connect is closed source, there is no public commit, diff or changelog. The fix ships only as vendor builds, and you confirm it by checking which build you are running.
What the bulletin covers
APSB26-191 is a large cumulative update fixing about two dozen Adobe Connect CVEs, including several other CWE-22 path traversal bugs, SSRF, SQL injection, XXE, CRLF injection, incorrect authorization and XSS. There is no standalone fix for CVE-2026-121349. Installing the update applies all of these fixes together. The bulletin lists this CVE as:
- Category: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-22
- Impact (per Adobe): Privilege escalation
- Severity: Critical, CVSS 3.1 base score 9.6
- Credit: reported by the researcher "edra", who also found 14 other issues in the same bulletin
Fixed builds
Each supported 12.x branch received its own patched build. The CNA record shown on NVD lists these as unaffected:
- 12.12 branch: 12.12 and earlier vulnerable, first fixed build 12.12.a
- 12.11 branch: 12.11 and earlier vulnerable, first fixed build 12.11.i
- 12.10 branch: 12.10 and earlier vulnerable, first fixed build 12.10.f
- 12.9 branch: 12.9 and earlier vulnerable, first fixed build 12.9.a
- 12.8 branch: 12.8 and earlier vulnerable, first fixed build 12.8.a
The letter suffix marks a patch build within a branch: 12.12 is vulnerable, 12.12.a is fixed. Compare the full build string, suffix included, rather than just major.minor. The bulletin's Solution section says Adobe recommends that users "update their installation to the newest version." Teams that must stay on an older branch can install that branch's lettered build instead, following the installation instructions in Adobe's Release Notes. The bulletin does not include a direct download link, and Adobe offers no temporary workaround.
How the fix likely works (not confirmed)
Adobe has published no technical details. For a CWE-22 bug, the standard fix is to resolve the user-supplied path to its canonical form first, then check that the result stays inside the allowed base directory, rejecting ../ sequences, encoded variants and absolute paths. That is the usual approach. Adobe has not confirmed that its fix works this way.
Detection methods
As of November 11, 2026, we found no published signature for CVE-2026-121349: no Snort or Suricata rule, no Sigma or YARA rule, no Nuclei template and no IoC list. OffSeq's Threat Radar lists the CVE's "Detectable" stage as having no evidence and notes that no public Nuclei template is indexed. Rapid7's vulnerability database entry repeats the CVE description and CVSS vector and gives no visible scanner check details. Detection therefore comes down to finding vulnerable builds, measuring exposure, and hunting for behaviour consistent with path traversal.
1. Version-based detection
This is the most reliable method. Adobe lists only Windows as the affected platform. The common mistake is checking only major and minor numbers. A server reporting 12.12 with no letter suffix is still vulnerable, and a rule like "12.12 or later" will wrongly mark it as patched. ThreatAft puts it directly: "A server reporting 12.12 is not patched."
- Compare the full version string, letter suffix included, against the fixed build for the matching branch.
- Check the version reported by the running application, not the installer's success message.
- Look for instances outside your CMDB. ThreatAft warns that Connect is often installed by learning or collaboration teams and then forgotten.
- Cloud instances hosted by Adobe are Adobe's to patch. Count the ones you run yourself, including Managed Services deployments.
2. Exposure assessment
The vector AV:N/AC:L/PR:L/UI:N/S:C means a network attacker with a low-privileged account can exploit the flaw without user interaction.
- Find every Connect endpoint reachable from the internet. Low privilege is a weak barrier on a platform that admits external attendees by design.
- Check whether the admin interface is reachable from the same network segment as the meeting service.
3. Behavioural hunting on the host
With no known URL or parameter, hunt for what a path traversal does rather than for a specific request. ThreatAft's guidance is that if EDR or file integrity monitoring covers the Connect host, you should look for the web process reading configuration files or credential stores outside the web root. A file read alert whose source process is the Connect web or application service and whose target is outside the Connect content and web directories is the clearest heuristic available. This guidance covers all four path traversal CVEs in APSB26-191 together, comes from an independent analyst, and has not been validated by Adobe.
4. Account and session integrity checks
Since Adobe says the flaw can give an attacker "elevated access or control over the victim's account or session," account-level evidence matters as much as file-level evidence. ThreatAft suggests:
- Look for admin accounts with no provisioning record.
- Look for meeting or library content that changed without a known owner.
Web logs may record nothing useful, especially if they are not forwarded to a central collector. Capture the running version string and the administrator list before applying the update so you have a baseline for comparison.
5. Generic path traversal monitoring (theory only)
The CAPEC patterns OffSeq links to this flaw (CAPEC-126, CAPEC-64, CAPEC-76, CAPEC-78/79) describe what to look for if you build your own WAF or log analytics rules for Connect traffic: dot-dot-slash sequences and their encoded or double-encoded forms in authenticated requests. Because the vulnerable endpoint is not public, such rules will be broad, noisy and unverified against this CVE. Treat them as hunting leads and combine them with the version check and host telemetry above.
Keep monitoring
Adobe's "not aware of exploits" statement and the CVE's absence from CISA KEV describe only November 11, 2026. Check the KEV catalog, the Adobe bulletin, and Nuclei and IDS rule feeds regularly. A public proof of concept will probably be followed quickly by real signatures.
Affected systems and versions
- Product: Adobe Connect
- Platform: Windows (the only platform Adobe lists as affected)
- Affected: Adobe Connect 12.12 and earlier
- Vulnerable branches and fixes:
- 12.12 is vulnerable, with the fix in 12.12.a
- 12.11 and earlier on that branch are vulnerable, with the fix in 12.11.i
- 12.10 and earlier on that branch are vulnerable, with the fix in 12.10.f
- 12.9 and earlier on that branch are vulnerable, with the fix in 12.9.a
- 12.8 and earlier are vulnerable, with the fix in 12.8.a
- Deployment notes: Cloud instances hosted by Adobe are patched by Adobe. Self-run installations, including Managed Services deployments, need to be verified against the build list above.
Vendor security history
Adobe's security overview for Connect describes application permissions separating customer accounts in its hosted service, web application firewall protections, security monitoring, internal and external penetration testing, and a process for evaluating and remediating reported vulnerabilities. These are Adobe's own descriptions rather than an independent assessment.
APSB26-191 itself is a large cumulative bulletin covering about two dozen Connect CVEs across several weakness classes, including multiple CWE-22 path traversal bugs. Fifteen of those issues, this one included, are credited to a single researcher, edra. The bulletin establishes a published remediation path, with fixes backported to five 12.x branches. One bulletin is not enough to characterize Adobe's broader track record, and the reviewed sources do not establish Connect's market position.
References
- NVD: CVE-2026-121349
- CVE Record: CVE-2026-121349
- Adobe Security Bulletin APSB26-191: Security update available for Adobe Connect
- Adobe Connect for training and webinars: Security
- Adobe Connect Security Overview (PDF)
- CISA Known Exploited Vulnerabilities Catalog
- ThreatAft: Adobe Connect, Six Perfect 10.0s in One Patch
- OffSeq Threat Radar: CVE-2026-121349
- Rapid7 Vulnerability Database: CVE-2026-121349
- SmartScope: Adobe Connect Windows multiple critical vulnerabilities, APSB26-191



