Automated Threat Modeling

Brief Summary: Adobe Connect CVE-2026-121352, a CVSS 10.0 Incorrect Authorization Flaw Enabling Privilege Escalation

A brief summary of CVE-2026-121352, an unauthenticated, network-reachable Incorrect Authorization flaw (CWE 863) in Adobe Connect rated CVSS 10.0. Covers the known attack conditions, affected versions, and the fixed builds Adobe shipped in APSB26-191.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Connect CVE-2026-121352, a CVSS 10.0 Incorrect Authorization Flaw Enabling Privilege Escalation

Introduction

Adobe has patched an Incorrect Authorization flaw in Adobe Connect that an unauthenticated attacker can reach over the network to escalate privileges and gain access to sensitive resources, with no user interaction required. With a CVSS 3.1 score of 10.0 and a changed scope, CVE-2026-121352 sits at the top of the severity scale. It shipped alongside four other maximum-severity Connect bugs in the same bulletin, APSB26-191.

Adobe Connect is Adobe's platform for virtual training and webinars, with virtual rooms and a purpose-built virtual learning environment. Adobe does not break out Connect revenue or market share. The parent company reported Digital Media annual recurring revenue of $19.20 billion at the end of fiscal 2025, up 11.5 percent year over year, but that figure speaks to the vendor's scale rather than Connect's own footprint. Connect is a server product that organizations expose to trainees and webinar attendees, so its authorization logic sits directly on the boundary between outside users and protected resources.

Technical information

Root cause

The CVE record classifies the issue as CWE 863, Incorrect Authorization. This class differs from a missing authorization check. The server does run a check, but the check reaches the wrong decision for some requests. In practice, a caller who should be denied access to a protected resource or action is allowed through instead.

Adobe has not published a source diff, commit, or technical write-up of the change, and the bulletin does not identify the affected endpoint, component, or permission check. We therefore cannot point to the specific faulty logic, and we have not reproduced any code here. What we can describe precisely is the attack surface Adobe assigned through its CVSS vector:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
  • AV:N (Network): the flaw is reachable remotely over the network.
  • AC:L (Low complexity): no special conditions beyond reaching the server are required.
  • PR:N (No privileges): the attacker does not need an account or session.
  • UI:N (No user interaction): no victim needs to click, join, or approve anything. The CVE description confirms this separately.
  • S:C (Scope changed): the impact extends beyond the security scope of the vulnerable component.
  • C:H / I:H (High confidentiality and integrity): successful exploitation can expose and modify protected data or actions.
  • A:N (No availability impact): the flaw is not rated as a denial-of-service vector.

PR:N paired with a privilege escalation outcome means an unauthenticated request ends up treated as authorized for something it should not reach.

Attack flow

Based only on the vector and the vendor description, exploitation would follow this general shape:

  1. The attacker identifies a network-reachable Adobe Connect server on Windows running a build at or below 12.12 without the APSB26-191 security suffix.
  2. Without credentials and without involving any user, the attacker sends requests to the server that are subject to the flawed authorization decision.
  3. The server's authorization check incorrectly permits the request, granting access to a resource or action reserved for a higher privilege level.
  4. The attacker gains elevated privileges and unauthorized access to sensitive resources, with high confidentiality and integrity impact that crosses into a different security scope.

The specific requests, parameters, and resources involved have not been disclosed, and no verified proof of concept was available to us.

APSB26-191 also fixes a sibling Incorrect Authorization bug, CVE-2026-121355 (CVSS 9.1). Both it and CVE-2026-121352, along with most of the bulletin's 24 CVEs, were credited to the researcher "edra". Five of the 24 CVEs, including this one, score CVSS 10.0.

Patch information

Adobe fixed CVE-2026-121352 in APSB26-191, published November 10, 2026. Connect is proprietary, so the fix arrives as vendor-built server updates rather than a public code change. Adobe shipped fixes on each supported release line instead of a single cumulative version. The CNA-supplied affected products data on NVD maps them as follows:

  • 12.12 line: vulnerable at 12.12 and below, first fixed build 12.12.a
  • 12.11 line: vulnerable at 12.11 and below, first fixed build 12.11.i
  • 12.10 line: vulnerable at 12.10 and below, first fixed build 12.10.f
  • 12.9 line: vulnerable at 12.9 and below, first fixed build 12.9.a
  • 12.8 line: vulnerable at 12.8 and below, first fixed build 12.8.a

heise and Rocket Boys' Security Measures Lab report the same five fixed versions.

A few practical notes:

  • Build suffixes. The lettered suffix marks a security update within a release line, so a server on 12.10 needs 12.10.f, not just any 12.10 build. Moving to the latest build on your current line resolves the issue without a major-version upgrade, though you should still check Adobe's release notes for your line.
  • Bundling. There is no standalone hotfix for this CVE. Installing the fixed build for your line closes CVE-2026-121352 and the rest of the 24 CVEs in the bulletin together.
  • Priority and exploitation status. Adobe assigned the update Priority 2 and states it is not aware of exploits in the wild for any issue in the bulletin. Rocket Boys notes that Priority 2 guidance means installing within roughly 30 days. Given the unauthenticated, network-reachable CVSS 10.0 profile, internet-facing Connect servers are reasonable candidates to patch sooner. The reviewed sources name no threat actors and document no public exploit code or campaigns.
  • Verifying the fix. With no public code change to diff against, the reliable check is the server's build string. Confirm each Connect server reports the patched build for its line (for example, 12.12.a). A server still reporting a plain base version such as 12.12 remains vulnerable.

Adobe has not published a workaround or configuration mitigation for this CVE, so applying the fixed build is the only vendor-confirmed remediation.

Affected systems and versions

  • Product: Adobe Connect
  • Platform: Windows
  • Affected per Adobe bulletin APSB26-191: Adobe Connect 12.12 and earlier
  • Fixed builds: 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a

The sources disagree on one point. The CVE record's version data lists versions 0 through 12.8 as affected and 12.8.a as unaffected, which reads narrower than the bulletin's "12.12 and earlier." The NVD affected products mapping and Adobe's bulletin both cover all five release lines from 12.8 through 12.12. Since Adobe's bulletin is the vendor's authoritative release guidance, we recommend using it, not the narrower CVE record range, to scope remediation.

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