On this page (7 sections)

Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability tracked as CVE-2026-121889. The NVD record describes it as one that could result in privilege escalation, requires no user interaction, and has a changed scope. It carries a CVSS score of 10, the maximum.

A second record, CVE-2026-121356, has an identical description and score and points to the same Adobe bulletin. Anyone who runs Adobe Connect, or hosts it for clients, should treat both as in scope and check Adobe's bulletin for the exact versions and fixes.

What is known so far

The public record is thin. Both NVD entries were published on 2026-11-10 and carry the same one-sentence description. They reference a single Adobe bulletin, APSB26-191. The research available for this article does not list affected versions, fixed versions, a patch number, or any exploitation reports. Those details should be in Adobe's bulletin, so read it directly instead of relying on a summary.

Only one independent publisher covers this story so far. Treat anything beyond the points above as unconfirmed until Adobe or another primary source says more.

What SSRF means in plain terms

Server-Side Request Forgery (CWE-918) is a weakness where an application can be made to send network requests on an attacker's behalf. The request comes from the server itself, not the attacker's machine. That matters because the server often sits in a trusted network position. It may reach internal services, admin interfaces, or cloud metadata endpoints that the public internet cannot.

The record says the flaw could lead to privilege escalation and that the scope is changed. In CVSS terms, a changed scope means the impact can extend beyond the vulnerable component itself to other resources. Combined with no required user interaction, that is consistent with the top score. The research does not say whether authentication is required, so do not assume it is.

The research does not describe how the flaw is triggered, and this article does not speculate on it. Remediation does not depend on those details.

Who is realistically exposed

  • Organizations that self-host Adobe Connect for webinars, training or meetings, especially where the server is reachable from the internet.
  • Hosting providers and agencies that manage Connect deployments for clients.
  • Environments where the Connect server can reach internal systems, databases or cloud metadata services, since SSRF is most damaging when the server has broad network access.
  • Teams that rely on a past patch level. Every new bulletin needs its own version check, even if you were current before.

The research does not say whether Adobe-hosted Connect is affected; confirm with Adobe or your account contact.

How to check your exposure

  1. Open Adobe's APSB26-191 bulletin and note the affected and fixed Connect versions.
  2. Find your installed Connect version in the Connect administration console or your deployment records.
  3. Compare it with the bulletin. If you are on an affected version, plan the update immediately.
  4. Check whether the Connect server is exposed to the internet and which internal networks it can reach.
  5. Review outbound traffic from the Connect server for unexpected connections to internal addresses or metadata endpoints.
Tip. If you cannot find your version quickly, that is itself a finding. Record it in your asset inventory so the next bulletin takes minutes, not hours.

What to do now

  1. Read APSB26-191 and identify the fixed Adobe Connect version for your deployment.
  2. Schedule the update right away, starting with internet-facing servers. Take a backup or snapshot first.
  3. Restrict outbound traffic from the Connect server so it can reach only what it needs. Block access to internal management networks and cloud metadata addresses where possible.
  4. Put the server behind a reverse proxy or firewall and limit administrative interfaces to trusted networks or a VPN.
  5. Review web server and application logs since the bulletin date for unusual requests and for outbound connections to internal hosts.
  6. Rotate credentials and API keys the Connect server holds if you find signs of abuse or cannot rule it out.
  7. Track CVE-2026-121356 as well, since it shares the description, score and bulletin.
Caution. Updating Connect usually means a restart or maintenance window. Schedule it so live sessions are not interrupted, and test on a staging copy if you have one.

Detection and monitoring afterwards

Because SSRF abuse happens server-side, much of the evidence is in egress logs rather than in what visitors see. Watch for outbound requests from the Connect host to private address ranges, link-local addresses, or services it never normally contacts. Alert on new outbound destinations.

From the outside, you can still keep an eye on the basics. A security scan of your verified site and certificate, DNS and header monitoring help catch unexpected changes on public hosts, though they cannot see internal requests made by the server. For background on why a network-level filter helps but does not replace patching, see what a WAF is.

Bottom line

A CVSS 10 SSRF in Adobe Connect deserves fast attention, even though the public details are sparse. Get the version and fix information from Adobe's bulletin, patch, and tighten what the server is allowed to reach so that the next flaw of this kind has less to work with.

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.

  1. CVE-2026-121889: Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation.nvd.nist.gov ·
  2. CVE-2026-121356: Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation.nvd.nist.gov ·
  • Adobe Connect
  • SSRF
  • CVE-2026-121889
  • APSB26-191
  • critical