ADOBE CONNECT · CVE-2026-121889 · Vendor
FIX → 12.12.a +4 ✓ verified
Adobe Connect has a server-side request forgery flaw that lets an attacker make the server send requests on their behalf. The description says this can lead to privilege escalation and needs no user interaction.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-hosted Adobe Connect servers on Windows running 12.12 or earlier that are not on a patched build are affected. Adobe rates it critical (CVSS 10.0): network-reachable, no authentication, no user interaction. Adobe says it is not aware of exploitation. Teams that do not run Connect on their own Windows servers can skip it.
Who cares adobe-connect, self-hosted, windows
Upgrade to 12.12.a +4
Update Adobe Connect (Windows, on-prem) to the patched build for your branch: 12.12.a, 12.11.i, 12.10.f, 12.9.a or 12.8.a (Adobe APSB26-191).
Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. Exploitation of this issue does not require user interaction. Scope is changed.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.