VulnerabilityPublished 11 Nov 2026

CVE-2026-121355: Adobe Connect is affected by an Incorrect Authorization vulnerability that could result in privilege

Source GCVE Database

Compare

Authoritative record:CVE-2026-121355· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 11 Nov 2026, 01:47 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (adobe)	CVSS 3.1	9.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-4qhx-wjjg-3r2m

What to do

Affected software

Product	Affected	Fixed in
AdobeAdobe Connect	Affected <=12.8	Fixed in–
AdobeAdobe Connect	Affected <=12.9	Fixed in–
AdobeAdobe Connect	Affected <=12.10	Fixed in–
AdobeAdobe Connect	Affected <=12.11	Fixed in–
AdobeAdobe Connect	Affected <=12.12	Fixed in–

AI-suggested

Until a fix is available, organizations should monitor official Adobe security advisories for updates. Implementing network-level protections such as restricting access to Adobe Connect services may reduce exposure.

Description

Adobe Connect contains an Incorrect Authorization vulnerability (CVE-2026-121355) that allows an attacker to escalate privileges without user interaction. This flaw could enable unauthorized access to sensitive information or functionality within the application. The vulnerability is rated critical with a CVSS score of 9.1, indicating high impact on confidentiality and integrity. No affected versions or patch information are currently provided.

Impact

Successful exploitation of this vulnerability could lead to privilege escalation, allowing attackers to access sensitive information or perform unauthorized actions within Adobe Connect. The high CVSS score indicates a significant risk to confidentiality and integrity of the system. No impact on availability is noted. Since no user interaction is required, the attack surface is broad.

Summary

CVE-2026-121355 describes an Incorrect Authorization vulnerability in Adobe Connect. This vulnerability permits an attacker to gain elevated privileges, potentially accessing sensitive data or restricted functions. The exploit requires no user interaction and can be triggered remotely over the network. The CVSS 3.1 base score is 9.1, reflecting critical severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality and integrity. There is no information on fixed versions or available patches, and no known exploits in the wild have been reported.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 01:47 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats