Adobe Connect | Server-Side Request Forgery (SSRF) (CWE-918)
Adobe Connect 12.12 and earlier on Windows is affected. Fixed in 12.12.a, 12.11.i, 12.10.f, 12.9.a and 12.8.a.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Adobe Connect contains a Server-Side Request Forgery flaw that lets an attacker make the server send requests on their behalf, which can lead to privilege escalation. It can be reached remotely, without logging in and without any user action.
Read the original description
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.
Who should check
Teams running Adobe Connect 12.12 and earlier on Windows
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 12.12.a, 12.11.i, 12.10.f, 12.9.a, 12.8.a.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-121356 (Adobe Connect | Server-Side Request Forgery (SSRF) (CWE-918)), 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-121356 (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-121356 is not listed as of cve.now's last read. This KEV status is for CVE-2026-121356 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-121356 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-121356.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- 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
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121356
Is CVE-2026-121356 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: cve.now feed data
What does this mean?
Server-Side Request Forgery (SSRF) is a flaw that can make the server send requests it should not send. Adobe lists privilege escalation as the impact of this issue.Source: adobe.com
Which versions are affected by CVE-2026-121356?
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: cve.now feed data
Am I affected, and how do I check?
Adobe Connect 12.12 and earlier are listed as affected, and the condition given is Windows. To check, look up the installed Adobe Connect version on the server and compare it with the listed versions.Source: adobe.com
How do I fix CVE-2026-121356?
Upgrade to the fixed build for your release line: 12.12.a, 12.11.i, 12.10.f, 12.9.a, or 12.8.a. No workaround is listed in the checked data.Source: adobe.com