Automated Threat Modeling

Brief Summary: Adobe Connect CVE-2026-121354 Path Traversal (CWE-22) Fixed in APSB26-191

A brief summary of CVE-2026-121354, a critical path traversal flaw in Adobe Connect 12.12 and earlier on Windows, covering the conflicting impact ratings, fixed builds per release line, and practical detection options.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Connect CVE-2026-121354 Path Traversal (CWE-22) Fixed in APSB26-191

Introduction

Adobe's November 10, 2026 security bulletin for Adobe Connect, APSB26-191, bundles 24 CVEs. One of them, CVE-2026-121354, lets a network attacker reach files and directories outside the locations the application is meant to expose. The flaw needs no user interaction, carries a changed scope rating, and is labeled arbitrary code execution in Adobe's own bulletin entry, so self-hosted Connect servers on Windows deserve a place near the top of this patch cycle.

Adobe describes Connect as a platform for training and webinars, including a purpose-built environment for complex training. The affected product here is the Windows on-premises server, which organizations run themselves and therefore patch themselves.

Technical Information

Root cause

CVE-2026-121354 is classified as CWE-22, Improper Limitation of a Pathname to a Restricted Directory. Some piece of input reaches the filesystem layer as a path without being properly confined to the intended base directory. The CVE description says an attacker could use this to "access sensitive files and directories outside the intended access scope", that exploitation does not require user interaction, and that scope is changed.

Adobe Connect is closed source. Adobe has not published a diff, a commit, a root-cause write-up, the vulnerable endpoint, the affected parameter, or the request format. Anything more specific than the bug class would be speculation, and we are not going to supply it.

Scoring and impact: the sources disagree

The CVE record assigns CVSS 3.1 9.9 with this vector:

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

That decodes to a network attack vector, low attack complexity, low privileges required, no user interaction, changed scope, and high confidentiality, integrity and availability impact. The vector is broader than the prose, which only describes arbitrary file system read.

Adobe's bulletin entry for the same CVE labels the impact as arbitrary code execution. Our briefing's review of the bulletin also recorded a score of 10.0 with privileges required set to none:

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

Other coverage of the bulletin reports 9.9 with PR:L. None of the reviewed sources explains or reconciles the difference in score, privilege requirement, or impact label. Our recommendation is not to treat the lower score or the narrower file read description as definitive. The I:H and A:H ratings are consistent with Adobe's code execution label, and when ranking the update the more severe interpretation is the safer one.

Attack flow (class level)

Based only on the published vector and description, the attack shape looks like this:

  1. The attacker reaches an Adobe Connect for Windows server over the network. Per the CVE record vector, a low-privileged account is required. Per the bulletin vector as recorded in our briefing, no privileges may be needed.
  2. The attacker sends a request in which a value that the server converts into a filesystem path contains traversal sequences, such as parent directory segments or their encoded variants. The specific endpoint and parameter are not public.
  3. The server fails to confine the resolved path to its intended directory and reads a file outside that boundary.
  4. Contents of sensitive files and directories outside the intended scope are exposed. Because scope is changed, the impact extends beyond the Connect component itself, and Adobe's bulletin characterizes the end result as arbitrary code execution.

No verified proof of concept, Metasploit module, Exploit-DB entry, or Nuclei template exists for this CVE at the time of writing.

Patch Information

Adobe fixed CVE-2026-121354 in APSB26-191, published November 10, 2026. The bulletin covers Adobe Connect 12.12 and earlier on Windows, carries Adobe's Priority 2 rating (which Adobe's guidance defines as action within 30 days), and contains 24 CVEs. The issue was reported by the researcher "edra", who is credited with 15 of the 24.

Adobe services several Connect release lines in parallel, so each line has its own fixed build. The CNA-supplied affected and unaffected data on NVD maps them as follows, and heise's coverage lists the same builds:

  • 12.8 line: 12.8 and earlier affected, first fixed build 12.8.a
  • 12.9 line: 12.9 and earlier affected, first fixed build 12.9.a
  • 12.10 line: 12.10 and earlier affected, first fixed build 12.10.f
  • 12.11 line: 12.11 and earlier affected, first fixed build 12.11.i
  • 12.12 line: 12.12 and earlier affected, first fixed build 12.12.a

The letter suffix marks a hotfix build within a release line. For example, 12.10.f is a later patch level of 12.10, not a new feature release. An install is only fixed if it runs the lettered build listed for its own line.

Adobe has not confirmed how the code was changed, and no patch snippet is public. Path traversal fixes are usually some combination of the following, which we list as inferred from the bug class rather than from Adobe's code:

  • Canonicalizing the requested path, resolving .. and . segments, symlinks, and encoded separators.
  • Checking that the resolved path still starts with the allowed base directory.
  • Rejecting absolute paths, drive letters, UNC paths, and alternate separators. On Windows, both \ and / act as separators.
  • Replacing user-supplied path fragments with server-side identifiers.

The same builds also fix three other CWE-22 path traversal flaws, CVE-2026-121351 (CVSS 10.0), CVE-2026-121906 (9.9) and CVE-2026-121349 (9.6), along with SSRF, XXE, SQL injection, CRLF injection, authorization and XSS bugs. CVE-2026-121354 is not patched on its own. Upgrading to the fixed build for your line closes the whole group. Adobe has not published a workaround or configuration-only mitigation.

Detection Methods

Public coverage. As of November 11, 2026, no signature exists for CVE-2026-121354. OffSeq's Threat Radar records no public Nuclei template, no Metasploit or Exploit-DB code, no CISA KEV listing, and no attack traffic on its Mirage honeypot sensors. Rapid7's database entry lists description and CVSS data only, with no check logic or module. No CVE-specific IoCs, YARA, Sigma, or Snort/Suricata rules have been published, so validate anything claiming to target this CVE against vendor or researcher sources first.

1. Version-based exposure detection. This is the most reliable method today. A server reporting a plain release line number such as 12.12 is vulnerable; 12.12.a is fixed. If your inventory or scanner compares only major and minor numbers, it will treat every 12.12 server the same, so make sure the full version string, suffix included, is captured. For ranking findings:

  • AV:N, AC:L and UI:N mean internet-exposed Connect servers go first.
  • PR:L means exposure is wider wherever Connect allows self-registration or broad guest access.
  • SmartScope suggests three triage steps: confirm whether you run Connect on your own Windows servers, check whether the version is 12.12 or earlier, and prioritize internet-facing instances.
  • The bulletin lists only the Windows on-premises product and does not say whether the hosted service is affected, so do not assume cloud tenants are covered by your scans.

2. Behavioral hunting for the path traversal class. Without a known endpoint or parameter, hunt for the general shape and effects of the attack:

  • Web and proxy logs. OffSeq maps this weakness to CAPEC-126 (path traversal), CAPEC-64 (slashes combined with URL encoding) and CAPEC-78/79 (escaped or alternately encoded slashes). Look for parent directory sequences and their encoded or double-encoded forms in query strings, POST bodies and path segments on Connect requests, especially from authenticated sessions. Decode and canonicalize request data before matching, or encoded variants will slip past simple string searches.
  • Session correlation. Tie attempts to real accounts. Low-privileged or newly created accounts that suddenly issue unusual requests resembling file access are worth attention. Many such requests from one account in a short window are a stronger signal than a single odd request.
  • Endpoint and EDR telemetry. Baseline the files the Connect server process normally touches, then alert on reads outside its install and content directories, such as OS configuration, other applications' configuration, or credential material. The changed scope rating is why host-level file access monitoring matters here.
  • Response anomalies. Successful arbitrary file reads often produce responses whose size or content type does not fit the requested resource. Compare file-serving response sizes against your baseline.

Attribution caveat. Because APSB26-191 fixes several other traversal CVEs plus SSRF, XXE and SQL injection flaws, a generic traversal hit cannot be attributed to CVE-2026-121354 specifically. Treat any such hit on an unpatched server as a possible attack against the whole group. Recheck OffSeq and Rapid7 periodically, since a public template or scanner check would change what you can detect.

Affected Systems and Versions

  • Product: Adobe Connect on Windows (on premises)
  • Affected: Adobe Connect 12.12 and earlier
  • Per line: 12.8 and earlier, 12.9 and earlier, 12.10 and earlier, 12.11 and earlier, and 12.12 and earlier, unless running the fixed hotfix build for that line
  • Fixed: 12.8.a, 12.9.a, 12.10.f, 12.11.i, 12.12.a
  • Hosted service: not addressed by the bulletin. Exposure cannot be determined from the available sources.

Vendor Security History

Adobe is the CNA for this CVE and runs a PSIRT that operates its vulnerability disclosure program, encourages private disclosure, and lists [email protected] as a contact. Adobe's Connect security overview describes development security activities, incident response, testing, vulnerability assessment and remediation planning, and for the hosted service, network segmentation, web application firewalls and continuous monitoring. These are Adobe's stated controls, not independent evidence about this flaw.

APSB26-191 itself is a sizable release: 24 CVEs, including four CWE-22 issues. The disagreement between the bulletin and the CVE record on score, privileges and impact for this CVE should stay visible in risk communication until one of them is corrected.

Adobe states it is not aware of any exploits in the wild for the issues in APSB26-191, and no threat actor attribution appears in the official sources.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization