Automated Threat Modeling

Brief Summary: Adobe Connect CVE-2026-121887 XXE Flaw Leading to Code Execution (CVSS 9.9)

A brief summary of CVE-2026-121887, a CVSS 9.9 XML External Entity flaw in Adobe Connect 12.12 and earlier on Windows that a low-privileged user can use to reach arbitrary code execution. Covers the fixed builds per branch from APSB26-191 and practical detection guidance.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Connect CVE-2026-121887 XXE Flaw Leading to Code Execution (CVSS 9.9)

Introduction

Adobe Connect servers that organizations operate themselves contain an XML External Entity flaw that lets any authenticated, low-privileged user reach arbitrary code execution over the network, with no user interaction and a changed scope. Adobe rates CVE-2026-121887 at CVSS 3.1 9.9 and fixed it in APSB26-191, a cumulative bulletin that closes 24 CVEs across five supported release branches.

Adobe Connect is Adobe's virtual learning environment for training, webinars and meetings, which Adobe describes as purpose-built for high-stakes, complex training. Adobe reported fiscal 2025 revenue of 23,769 million dollars across its Digital Media, Digital Experience, and Publishing and Advertising segments, although the sources we reviewed give no Connect-specific market share figures. Connect is a server product that training or collaboration teams often install for one program and then leave running, so vulnerable instances can easily sit outside the CMDB and normal patch cycles.

Technical information

Root cause

The flaw is classified as CWE-611, Improper Restriction of XML External Entity Reference. XML documents may contain a Document Type Definition (DTD), and a DTD can define entities using a URI. A parser that does not restrict this behaviour will retrieve the URI contents and insert them into document processing.

In the XXE pattern, an attacker supplies a document whose <!DOCTYPE> declares external entities such as SYSTEM "file:///..." or SYSTEM "http://...". When the server-side parser resolves those entities, it can be made to read local files, send requests to internal hosts, or exhaust resources. MITRE lists those as the general consequences of the weakness class. For this specific CVE, Adobe rates the outcome as arbitrary code execution in the context of the current user, with impact that crosses the vulnerable component's security boundary (changed scope).

CVSS vector

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

  • AV:N: reachable over the network
  • AC:L: low attack complexity
  • PR:L: a low-privileged account is enough
  • UI:N: no user interaction required
  • S:C: scope is changed
  • C:H/I:H/A:H: high confidentiality, integrity and availability impact

What has not been disclosed

Adobe Connect is closed source, so there is no public commit, diff or vulnerable code snippet. Neither the CVE record nor the APSB26-191 bulletin identifies the vulnerable XML entry point, the parser in use, a specific attack request, or how entity resolution leads to code execution. The evidence supports a description of the bug class and its rated outcome, but not a precise exploit recipe.

Attack flow

Based on the published vector and the description of the bug class, exploitation proceeds roughly as follows:

  1. The attacker holds a low-privileged account on a vulnerable Connect server (PR:L).
  2. The attacker sends XML to a Connect function that parses it. The document carries a <!DOCTYPE> declaring an external entity that points to a local file (file:///) or a remote or internal URL (http://). Adobe has not said which function this is.
  3. The server's XML parser resolves the external entity, causing it to read local resources or make outbound requests on the attacker's behalf.
  4. Per Adobe's rating, exploitation can result in arbitrary code execution in the context of the current user, with impact extending beyond the vulnerable component. Adobe has not described the mechanism that turns entity resolution into code execution.

APSB26-191 also fixes CVE-2026-121890, a second XXE issue in Connect that Adobe rates High (7.7) with an arbitrary file system read impact. The same researcher, "edra", reported both XXE bugs and many of the other critical issues in the bulletin.

Patch information

Adobe fixed CVE-2026-121887 in security bulletin APSB26-191, published November 10, 2026. Adobe rates the update Priority 2 and recommends that customers update to the newest version. Because the product is closed source, the fix ships only as vendor builds.

Adobe's CVE record and the NVD entry map each vulnerable branch to its own fixed build. Moving to the fixed build on the branch you already run is enough. You do not have to jump to the newest major line.

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

The update goes on the Connect server installation itself. Meeting attendees do not need to update their clients for this fix. After patching, check the build string on the server against the list above. Branch letters such as .f or .i show how many updates a branch has received, so a server on 12.10.e, for example, is still vulnerable.

Adobe has not said which XML handling component it changed or how. As general context for the bug class (not a confirmed description of Adobe's change), XXE fixes usually harden the parser so it no longer resolves external entities, by:

  • refusing DTD declarations outright,
  • turning off external general and parameter entities, or
  • blocking external DTD loading and entity URL resolution.

APSB26-191 is cumulative and fixes 24 CVEs at once, including SSRF, path traversal, SQL injection, incorrect authorization, CRLF injection, code injection and XSS alongside the two XXE issues. The CVE-2026-121887 fix cannot be installed on its own, but a single upgrade to a fixed build closes the whole set.

At release, Adobe stated it was not aware of any exploits in the wild for these issues, and CISA's SSVC enrichment of the CVE record lists exploitation as "none". Both reflect what Adobe knew at the time and do not independently verify that no activity has occurred. The sources we reviewed do not establish whether public exploit code exists.

Detection methods

Nothing published so far is specific to this CVE. No vendor or researcher has released a Snort or Suricata rule, Sigma or YARA rule, Nuclei template, exploit-specific log pattern or IoC set for CVE-2026-121887. Since Adobe has not identified the Connect function that parses the malicious XML, defenders cannot match on a known endpoint or payload. The verified guidance comes down to version checks and behavioural hunting.

1. Find vulnerable builds using the full version suffix

The most reliable check today is version based: Adobe Connect 12.12 and earlier on Windows is affected, with fixed builds 12.12.a, 12.11.i, 12.10.f, 12.9.a and 12.8.a.

The catch is the letter suffix. ThreatAft points out that a server reporting plain 12.12 is still vulnerable while 12.12.a is fixed. A scanner, compliance check or SIEM rule that compares only the numbers ("12.12 or later") will mark an unpatched server as compliant. ThreatAft advises comparing the full version string, suffix included, and reading it from the running application rather than trusting the installer's success message. When building the check:

  • Include every on-premises instance, especially those outside the CMDB.
  • Treat Adobe's hosted Connect service separately. ThreatAft describes APSB26-191 as a customer action only for deployments your organization operates, including Managed Services.
  • Rapid7's vulnerability database has an entry for this CVE (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Before relying on any commercial scanner, confirm it understands the suffixed builds.

2. Prioritize by exposure

The vector shows the flaw is network reachable by a low-privileged user with no interaction. Layer exposure on top of the version check: identify which Connect endpoints are reachable from untrusted networks, and whether the admin interface is reachable from the same network as the user-facing meeting service. A vulnerable build reachable from the internet goes to the top of the list.

3. Hunt for XXE behaviour on the host

With no payload to match, ThreatAft recommends hunting for effects. A successful XXE typically causes the server to read local files or make outbound requests it would never normally make:

  • File reads outside the web root: if EDR or file integrity monitoring covers the Connect host, look for the Connect web process reading configuration files or credential stores.
  • Unexpected outbound connections from the Connect server: ThreatAft cites this as evidence for the bulletin's SSRF flaws, and it applies to XXE too, since a common XXE technique has the parser fetch a remote resource. Look for connections to internal addresses, cloud metadata services or unfamiliar external hosts, and review egress so you know which destinations are legitimate.
  • After patching, check whether anything already happened: look for administrator accounts with no provisioning record, and content library or meeting archive changes no legitimate owner can explain. This advice covers the whole bulletin, but it is relevant here because this XXE is rated as leading to code execution.

No source provides a validated query, process name, file path or signature for these hunts. You will need to adapt them to your own EDR and log pipeline and baseline the Connect process's normal file and network activity.

4. Know what the logs may not show

ThreatAft warns that injection-style attacks can succeed without producing an application error, and a malicious outbound request may be logged as an ordinary connection. If Connect's web logs are not shipped to a central collector, the only lasting evidence may be database state and the account list. Before upgrading, capture the running version string and the current administrator list as a baseline.

Affected systems and versions

  • Product: Adobe Connect (server installations), on Windows
  • Affected: Adobe Connect 12.12 and earlier
  • Per branch: 12.8 and earlier (fixed in 12.8.a); 12.9 and earlier (fixed in 12.9.a); 12.10 and earlier (fixed in 12.10.f); 12.11 and earlier (fixed in 12.11.i); 12.12 and earlier (fixed in 12.12.a)
  • Still vulnerable examples: a build reporting plain 12.12, or 12.10.e
  • Configuration notes: customer action applies to deployments your organization operates, including Managed Services. Adobe's hosted Connect service should be treated separately. Meeting attendee clients do not need updating for this fix.

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