On this page (7 sections)
Adobe Connect, the web conferencing and virtual classroom platform, has been hit by a group of SQL injection vulnerabilities published on 2026-11-10. The lead entry, CVE-2026-121908, is described as allowing arbitrary code execution in the context of the current user, and it is rated CVSS 9.9 (critical).
If your organization hosts or administers Adobe Connect, treat this as a priority to review. Three of the four related records carry the same description and score, and a fourth, CVE-2026-121894, is worded slightly differently. The research available to us is thin, so this article separates what is confirmed from what is not yet stated.
What happened
Four CVE records published on 2026-11-10 describe SQL injection in Adobe Connect. The three records we have scores for share an identical description: an improper neutralization of special elements in an SQL command that could result in arbitrary code execution in the context of the current user. Their reference points to Adobe's security bulletin APSB26-191, which is the place to confirm affected and fixed versions.
The fourth record, CVE-2026-121894, differs in its stated impact. It says a low-privileged attacker could execute arbitrary SQL commands, potentially gaining elevated access or control over the victim's account or session. Its CVSS score is not included in the research we have.
Technical details
SQL injection happens when an application builds a database query using input it did not properly clean, so special characters in that input are interpreted as part of the query instead of as plain data. The weakness class is CWE-89. Normally the result is data exposure or tampering. Here the records say the outcome can go further, to arbitrary code execution.
The records give these traits for the three scored CVEs:
- A low-privileged attacker is enough, so a normal or guest-level account may be sufficient.
- No user interaction is required, so no one has to click a link or open a file.
- Scope is changed, meaning the impact can reach beyond the vulnerable component itself.
- Code runs in the context of the current user.
These traits explain the 9.9 score. The records do not say whether the attack comes over the network, how the vulnerable parameters are reached, or which Connect components are involved, and we will not guess at them.
Who is affected
The records name Adobe Connect without listing versions. Until you have checked APSB26-191, assume any self-managed Connect deployment could be in scope. Exposure is greater when:
- Connect is reachable from the internet, for example for customers, students or external meeting guests.
- Many users hold low-privileged accounts, such as registered attendees or trainees.
- The server has network access to internal systems, which matters because the scope is changed.
- Patching of the Connect server is handled outside your normal update routine.
If your Connect service is fully managed and updated by Adobe, confirm with the vendor what has already been applied rather than assuming.
How to check your exposure
- Open Adobe's bulletin APSB26-191 and read the affected and fixed versions.
- Find the version your Connect server is running in the Connect administration interface or your deployment records.
- Compare the two. If your version is in the affected range, plan the update right away.
- List who can reach the server and which accounts exist. Remove unused low-privileged accounts and review recent signups.
Also look at the web server and application logs for anything unusual in the period before you patch. Typical signs of SQL injection attempts are database error messages in responses, bursts of requests from one address to the same endpoint, and unexpected characters such as quotes or SQL keywords in request parameters. This kind of log review is a general hardening step, not a confirmed indicator for these specific CVEs, as the research gives no indicators of compromise.
What to do now
- Read APSB26-191 and identify the fixed Adobe Connect version for your deployment.
- Schedule and apply the update as soon as possible, starting with internet-facing servers.
- Take a backup of the Connect server and its database before updating, so you can roll back if needed.
- Until patched, limit access to Connect to the networks and users that need it, for instance by restricting guest access or placing it behind a VPN.
- Review accounts and remove unused or unknown low-privileged users.
- Make sure the database account used by Connect has only the permissions it needs.
- Check web and database logs from before the update for suspicious requests or errors.
- If you find signs of compromise, rotate credentials and follow an incident process before returning the server to service.
Detection and monitoring afterwards
After patching, keep watching for follow-up activity. Webforta's security scans can check verified sites for externally visible problems, and monitoring can alert you to unexpected changes in availability, certificates, DNS and headers on your Connect host. Neither can confirm whether this specific flaw is present or exploited, so version checks against Adobe's bulletin remain the authoritative test.
Also watch for new announcements. The related records may be updated with versions, scores or exploitation notes, and a CISA KEV listing would be a sign that attacks are underway. At the time of writing, none of the records is marked as listed there. If you suspect a compromise, follow our guide on what to do when a website is hacked.
Timeline
| Date | Event |
|---|---|
| 2026-11-10 | NVD publishes CVE-2026-121908, CVE-2026-121898, CVE-2026-121896 and CVE-2026-121894, referencing Adobe bulletin APSB26-191 |
No other dates, such as discovery, patch release or first exploitation, are given in the research.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
- CVE-2026-121908: Adobe Connect is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in…
- CVE-2026-121898: Adobe Connect is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in…
- CVE-2026-121896: Adobe Connect is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in…
- CVE-2026-121894: Adobe Connect is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in…
