Introduction
Adobe's November 10, 2026 security bulletin for Connect fixed an SQL injection flaw that, by Adobe's own scoring, can be reached over the network with no credentials and no user interaction, and that could result in arbitrary code execution. For organizations running Adobe Connect servers for training, webinars or internal collaboration, CVE-2026-121902 puts the application database, and potentially the host itself, within reach of anyone who can connect to the server.
Adobe Connect is Adobe's web conferencing and virtual classroom platform. Adobe describes it as a purpose-built virtual learning environment for complex training and markets it to trainers and marketers for training and webinars. The sources we reviewed do not quantify its market share or customer count, so we will not estimate its scale. Its relevance comes from where it tends to sit. Connect servers are often stood up by training or collaboration teams, can live outside central asset inventories, and hold user accounts, meeting archives and content libraries.
Adobe rates the issue Critical with a CVSS 3.1 score of 9.4 and says it is not aware of exploitation in the wild for any issue in the bulletin.
Technical information
Root cause
CVE-2026-121902 is classified as CWE-89, improper neutralization of special elements used in an SQL command. In practical terms, input that reaches the application ends up inside an SQL statement without being safely separated from the query structure, which lets an attacker change what the database executes. Adobe's description says an attacker could exploit the flaw to execute arbitrary SQL commands, compromising the confidentiality, integrity and availability of the application, and that the issue could result in arbitrary code execution.
That is where the public detail ends. Adobe has not disclosed which endpoint, parameter or query is vulnerable. Connect is closed source, so there is no public commit, diff or pull request to inspect, and no vulnerable code snippet is available. We also found no verified proof of concept or exploitation write-up.
What the CVSS vector tells us
Adobe's bulletin assigns the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L:
- AV:N (Network): the vulnerable code is reachable remotely.
- AC:L (Low complexity): no special conditions are needed beyond reaching the vulnerable input.
- PR:N (No privileges): no account or login is required.
- UI:N (No user interaction): no victim needs to click or open anything.
- S:U (Unchanged scope): impact is scored against the Connect application itself.
- C:H / I:H / A:L: high confidentiality and integrity impact, low availability impact.
The vendor assigned these characteristics to rate severity. They are not evidence that exploitation has occurred.
Likely attack flow
Based only on the vector and the vendor description, the attack would likely go like this:
- The attacker identifies an Adobe Connect server reachable over the network. Because the vector is AV:N with PR:N, an internet-facing instance is the most exposed case.
- The attacker sends a crafted request carrying SQL syntax to the vulnerable input. No authentication and no action by any user is required.
- The injected SQL runs in the context of the Connect database. Given the high confidentiality and integrity ratings, this could expose or alter stored data. ThreatAft's hunting guidance notes that SQL injection in Connect reaches the user table, which is why unexpected administrator accounts are the main artifact to look for.
- Adobe classifies the impact as arbitrary code execution. The specific path from SQL execution to code execution has not been disclosed, so we cannot describe it.
Patch information
Adobe fixed CVE-2026-121902 in security bulletin APSB26-191, published November 10, 2026, with Adobe priority rating 2. The bulletin lists the CVE as a Critical SQL Injection (CWE-89) with arbitrary code execution impact and the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L (9.4). It is one of 24 CVEs fixed in the same update, so applying the patch also closes the other SSRF, path traversal, XXE, SQL injection and XSS issues in the bulletin.
A hotfix for each release line
Adobe did not require a move to a single new version. It shipped a lettered hotfix for each supported 12.x line, and each hotfix is the first build on that line that is no longer vulnerable. Adobe's CVE record, mirrored by NVD, maps them as follows:
| Release line | Vulnerable | First fixed build |
|---|---|---|
| 12.12 | 12.12 and earlier | 12.12.a |
| 12.11 | 12.11 and earlier | 12.11.i |
| 12.10 | 12.10 and earlier | 12.10.f |
| 12.9 | 12.9 and earlier | 12.9.a |
| 12.8 | 12.8 and earlier | 12.8.a |
The letter after the version number counts hotfixes within a line. For example, 12.11.i is later than 12.11.a through 12.11.h. A server on 12.11.h may look current but is still affected. Only 12.11.i or later contains the fix. The bulletin lists Windows as the affected platform and does not say whether Adobe's hosted Connect service is affected or how it is patched.
What the patch changes
Adobe has not said which endpoint, parameter or query was vulnerable, or how the code was changed. Because the product is closed source, we cannot confirm whether Adobe moved to parameterized queries, added input validation or allow-listing, or tightened database permissions. Those are the usual fixes for CWE-89, but there is no direct evidence for any of them. Treat the hotfix build number as the only proof that the fix is in place.
Checking the fix in vulnerability feeds
The GitHub Advisory Database entry (GHSA-w7r6-j6mh-mqfw) is unreviewed and its patched versions field is empty, so tools that rely only on GHSA will not show a fixed version. Use the CVE.org/NVD record or Adobe's bulletin instead. Those records mark each line's lettered build as unaffected and everything up to the base version as affected.
Credit
Adobe credits Jim Green (green-jam) with reporting CVE-2026-121902. In the same bulletin he is also credited with CVE-2026-121906, CVE-2026-121908, CVE-2026-121910 and CVE-2026-121912.
Detection methods
No public exploit signature exists for CVE-2026-121902. We found no CVE-specific Snort or Suricata rule, Sigma or YARA rule, WAF signature, request pattern, or atomic indicator such as hashes, IPs or domains. One upstream claim pointed to DCRat YARA signatures, but none of the material tied to this CVE supports that. For now, detection has three parts: confirm which servers are vulnerable, find where those servers can be reached, and check exposed servers for signs the bug has already been used.
1. Version checks: the suffix decides patch status
Because each line has its own lettered fix, you cannot judge a server from major.minor alone. A server reporting plain 12.12 is vulnerable, and 12.12.a is fixed. ThreatAft's analysis warns that a scanner comparing integers against 12.12 "will show green" on a server that is still exposed, and recommends a string comparison on the full version including the letter suffix. Apply that logic in compliance checks, CMDB queries and any SIEM rule that reads installed software versions.
2. Commercial scanner coverage
Tenable's Nessus plugin 378192 (adobe_connect_apsb26-191.nasl, family CGI abuses, published 11/10/2026) lists CVE-2026-121902 with the rest of the APSB26-191 set. Two limits apply:
- It reads the version and does not test the flaw. Tenable states the check relies only on the version number the application reports about itself. A positive result means the server reports a vulnerable version. It does not mean the server is exploitable or has been attacked. The plugin needs the
installed_sw/Adobe ConnectKB item, so the product must be identified first. It works with remote scans and Nessus Agents. - Check how it handles unsuffixed 12.12. The plugin is titled for Connect 12.11 and earlier and flags versions prior to 12.12, while vendor and NVD data list unsuffixed 12.12 as affected. Before trusting a clean result, compare plugin output against a manual check of the full build string on any 12.12 hosts.
Rapid7's vulnerability database also has an entry for CVE-2026-121902. The public page does not describe how the check works, so confirm coverage in your own InsightVM/Nexpose content before relying on it.
3. Exposure discovery
With a vector of AV:N/AC:L/PR:N/UI:N, network reachability determines how urgent each server is. IONIX recommends limiting network access to Connect instances and monitoring for suspicious activity until they are patched. ThreatAft's hunt guidance suggests:
- Listing every Connect instance, including ones outside the CMDB, such as a server stood up by a training or collaboration team for a single webinar series.
- Determining which Connect endpoints are reachable from the internet, and whether the admin interface shares a network with the user-facing meeting service.
- Separating on-premises and Managed Services deployments (your responsibility) from Adobe-hosted cloud (patched by Adobe).
External attack surface tools can help with discovery. IONIX advertises discovery of internet-facing assets and nonintrusive validation, but has not published a payload for this CVE.
4. Compromise assessment
Without a request signature, look for the effects of a successful injection. ThreatAft's integrity review after patching focuses on:
- Unknown admin accounts. SQL injection reaches the user table, so an administrator with no provisioning record is the primary warning sign.
- Content changed with no clear owner. Look for changes to the meeting archive or content library that cannot be traced to a legitimate account.
- Unusual behavior by the Connect process. Because the CVE can lead to code execution, use EDR to watch for the Connect web process reading configuration or credential files, or making unexpected outbound connections to internal addresses.
Logs alone may not catch it. ThreatAft points out that an SQL injection can succeed without producing an application error. If Connect web logs are not shipped to a central collector, the only lasting evidence may be database state and the account list. Record the full version string and administrator list before upgrading so you have a baseline to compare against.
A packet- or log-level signature will only be possible once the vulnerable endpoint or parameter is disclosed through a researcher write-up, a PoC or vendor IDS content. Keep watching the Adobe bulletin, CISA KEV and IDS vendor rule releases, and replace the indirect hunting above with exact request matching when that content appears.
Affected systems and versions
Adobe Connect on Windows, per APSB26-191:
- 12.12 and earlier on the 12.12 line (fixed in 12.12.a)
- 12.11 and earlier on the 12.11 line, including lettered builds before 12.11.i such as 12.11.h (fixed in 12.11.i)
- 12.10 and earlier on the 12.10 line (fixed in 12.10.f)
- 12.9 and earlier on the 12.9 line (fixed in 12.9.a)
- 12.8 and earlier on the 12.8 line (fixed in 12.8.a)
The most exposed configuration is any on-premises or Managed Services deployment reachable over the network, since no authentication or user interaction is required. The bulletin does not state whether Adobe's hosted Connect service is affected.
Vendor security history
Adobe maintains a public security bulletins and advisories page describing vulnerabilities in specific product versions and the corrective actions for each, and it runs private and public vulnerability disclosure and bug bounty programs. APSB26-191 itself was a large release for Connect: 24 CVEs covering SSRF, path traversal, XXE, SQL injection and XSS, with five of them credited to the same researcher. These facts show that Adobe has established disclosure and response channels. The reviewed sources do not provide enough data to grade Adobe's broader security track record.
References
- NVD: CVE-2026-121902 Detail
- CVE.org record for CVE-2026-121902 (API)
- Adobe Security Bulletin APSB26-191: Security update available for Adobe Connect
- GitHub Advisory GHSA-w7r6-j6mh-mqfw
- GitHub Advisory API: GHSA-w7r6-j6mh-mqfw
- Tenable Nessus Plugin 378192
- Rapid7 Vulnerability Database: CVE-2026-121902
- ThreatAft on dev.to: Adobe Connect APSB26-191 and the version suffix scanner issue
- ThreatAft: Adobe Connect APSB26-191 mass disclosure of 24 CVEs
- IONIX Threat Center: CVE-2026-121902
- SmartScope: Adobe Connect Windows multiple critical vulnerabilities (APSB26-191)
- Threat Radar: CVE-2026-121902 Adobe Connect SQL Injection
- Threat Radar: Adobe Connect Improper Neutralization advisory
- Casco: CVE-2026-121902
- Adobe Connect for training and webinars
- Adobe Trust Center: Security bulletins and advisories
- Adobe Security Blog: Public vulnerability disclosure program becomes a paid bug bounty program



