Somebody leaves the conference-room door open so anyone who knocks gets to rearrange the whole office
CVE-2026-48360 is a code-injection flaw (CWE-94) in the Adobe Connect Desktop Application for Windows (≤2026.8.51), Mac Silicon (≤2026.08.45), Mac Intel (≤2026.01.39), and the Android Mobile App (≤4.4). Attacker-controlled input reaches a code-generation path in the client — likely the embedded Chromium rendering engine or a custom URI/protocol handler — and is executed without proper neutralization. The CVSS vector marks Scope:Changed because the injected code escapes the application sandbox and runs at the operating-system level with the current user's privileges. Exploitation requires a single user interaction: the victim must click a malicious URL or visit a compromised web page that targets the desktop client's input-processing pipeline.
Adobe rates this 9.6 CRITICAL, and the CVSS math backs that up on paper (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H). In practice the score overstates the risk for most enterprises. First, this is a client-side vulnerability — it does not give unauthenticated remote access to a server. Second, the Adobe Connect desktop app has a modest installed base compared to Teams, Zoom, or WebEx; many Connect deployments are browser-only and never install the native client. Third, there is no public PoC, no known exploitation, and no EPSS score yet (the CVE was published yesterday). VulDB independently scored this at 7.9, which better reflects the real-world friction. We align closer to VulDB's reading: HIGH at 8.0.
4 steps from start to impact.
Deliver malicious URL to victim
connectpro://) registered by the app installer or a web page that hands off content to the desktop client through browser-to-app dispatch. The URL is delivered via phishing email, a watering-hole page, or a compromised meeting invitation. No authentication or network access to the target is needed — only the ability to reach the victim's inbox or browser.- Victim has an email address or browses attacker-influenced content
- Attacker can craft a URL that the Connect desktop app will process
- Email gateway may strip or sandbox unknown URI schemes
- Link-click rates on phishing campaigns average 3-8% in mature orgs
- Browser may prompt before handing off to external app (e.g., Windows 'Open with' dialog)
Adobe Connect desktop app processes malicious input
- Adobe Connect Desktop App is installed and registered as the handler for the relevant URI scheme or content type
- App version is vulnerable (Windows ≤2026.8.51, Mac Silicon ≤2026.08.45, Mac Intel ≤2026.01.39, Android ≤4.4)
- Many enterprises use browser-only Adobe Connect access and never deploy the desktop client
- The desktop app must be the registered handler — if it was uninstalled or superseded, the chain breaks
- Managed Chromium policies or enterprise app-control may restrict embedded engine behavior
AdobeConnectApp.exe or equivalent is a strong signal.Code injection achieves OS-level execution
- Steps 1 and 2 succeeded
- No application-level sandbox or code-signing enforcement blocks the injected payload
- Code runs as standard user, not SYSTEM/root — lateral movement requires additional privilege escalation
- macOS Gatekeeper and notarization checks may interfere with post-exploitation payloads
- Windows Defender / EDR behavioral detection may flag anomalous child-process chains from a meeting app
- Android sandboxing further constrains post-exploitation options
cmd.exe, powershell.exe, bash, or making anomalous network connections. AMSI on Windows can inspect script content before execution.Post-exploitation and lateral movement
- Step 3 succeeded
- Endpoint has accessible credentials or network paths to higher-value targets
- Credential Guard / LSASS protection limits credential theft on hardened Windows endpoints
- Network segmentation limits lateral reach
- MFA on downstream services blocks replayed credentials
- EDR should detect common post-exploitation frameworks (Cobalt Strike, Sliver, etc.)
connectpro:// (and any related) URI handlers registered by the Adobe Connect Desktop App. This breaks Step 2 of the attack path — the browser can no longer hand off to the vulnerable app. Users can still join meetings via the browser-based interface. Deploy within 30 days per noisgate mitigation SLA for HIGH.AdobeConnectApp.exe (or equivalent Mac/Android process) spawning cmd.exe, powershell.exe, bash, python, wscript, cscript, or making outbound connections to non-Adobe domains. This catches Step 3 post-exploitation. CrowdStrike, SentinelOne, and MDE all support custom IOA/behavioral rules.- Patching the Adobe Connect Server (12.x) does not fix this. The vulnerability is in the desktop client application, not the server. Upgrading your Connect server to 12.12 addresses other CVEs but leaves this client-side flaw open.
- Standard network segmentation does not help. The attack enters through a user clicking a URL — it does not traverse internal network boundaries in the initial exploitation phase.
- Web Application Firewalls (WAF) in front of your Connect server are irrelevant. The code injection occurs in the local desktop app's rendering engine, not in HTTP traffic to the server. WAF rules cannot inspect or block the malicious payload once the desktop app processes it locally.
- Disabling JavaScript in the browser does not help because the code injection occurs in the embedded Chromium engine inside the desktop app, not in the user's web browser.
The supporting signals.
| In-the-wild exploitation | None observed. Adobe states it is 'not aware of any exploits in the wild' for APSB26-182. OffSeq Mirage reports no attack traffic. Not in CISA KEV. |
|---|---|
| Proof-of-concept | No public PoC. No repositories on GitHub named after CVE-2026-48360. Not indexed on pocindex.io, Exploit-DB, or Metasploit. No Nuclei template available. |
| EPSS | Not yet scored. FIRST EPSS API returns empty data for this CVE (published 2026-10-27, likely too new for the daily model run). |
| KEV status | Not listed in CISA Known Exploited Vulnerabilities catalog as of 2026-10-28. |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H — 9.6. The Scope:Changed flag is the score amplifier; without it the base would be ~8.8. VulDB independently scores 7.9 under their own methodology. |
| Affected versions | Desktop App: Windows ≤2026.8.51, Mac Silicon ≤2026.08.45, Mac Intel ≤2026.01.39. Android Mobile App ≤4.4. |
| Fixed versions | Windows 2026.9.61, Mac Silicon 2026.10.66, Mac Intel 2026.10.170, Android 4.5. Bulletin APSB26-182, priority rating 2. |
| Exposure data | No GreyNoise or Shodan scanning data specific to this CVE. Adobe Connect has a niche market share in web conferencing — significantly smaller than Teams, Zoom, or WebEx. Many deployments are browser-only and do not install the desktop client. |
| Disclosure date | 2026-10-27 (CVE reserved 2026-05-21). NVD status: 'Received' — analysis pending. |
| Credited researcher | Credited to 'al' per Adobe's APSB26-182 bulletin. |
Sources.
- Adobe APSB26-182 Advisory (via SecurityOnline roundup)
- OffSeq Radar — CVE-2026-48360 Threat Intelligence
- Strix AI — CVE-2026-48360 Detail
- TheHackerWire — CVE-2026-48360 Analysis
- Adobe Connect Desktop App 2026.3 Release Notes
- Adobe Connect Security Bulletin APSB26-150 (September 2026)
- FIRST EPSS API — CVE-2026-48360 (no data yet)
Why this verdict
- User-interaction gate reduces weaponization efficiency. The victim must click a crafted link or visit a compromised page. While phishing is effective (3-8% click rates), this is a meaningful friction point that prevents mass-autonomous exploitation. Every successful attack requires a human decision — this caps the blast radius per campaign.
- Niche installed base shrinks the exposed population. Adobe Connect Desktop App has modest enterprise penetration compared to Teams or Zoom. Many Connect deployments are browser-only. The desktop client must be installed AND registered as the URI handler for the chain to fire. This is a fraction-of-a-fraction problem.
- No PoC, no exploitation, no EPSS — day-one disclosure. The CVE was published yesterday. There is zero evidence of weaponization, no public exploit code, and no scanner coverage. The threat is entirely theoretical as of today.
- Client-side execution at user privilege level. Code runs as the logged-in user, not SYSTEM or root. Lateral movement requires additional privilege escalation and credential harvesting — a multi-step chain beyond the CVE itself.
- Role multiplier: Adobe Connect Desktop App is a standard endpoint collaboration tool. It is NOT a canonically high-value component (not an IdP, hypervisor, PAM agent, backup server, network edge appliance, or kernel-mode agent). In the high-value role scenario — the app installed on a domain admin's workstation — the chain could theoretically reach DA through post-exploitation credential theft. However, <1% of Adobe Connect desktop installs occupy admin workstations, and this multi-hop scenario requires additional vulns/misconfigs beyond CVE-2026-48360. The direct blast radius is host-level compromise at standard user privilege. This does not trigger the CRITICAL floor.
Why not higher?
CRITICAL would require either (a) no user interaction, (b) a canonically high-value component where ≥10% of installs are in fleet-scale blast-radius roles, or (c) active exploitation evidence. None apply here. The desktop app is an endpoint client, the attack requires a click, and there is zero exploitation activity. VulDB's independent 7.9 score and the niche installed base confirm that 9.6 overstates the real-world risk.
Why not lower?
MEDIUM would understate the threat because the vulnerability delivers full code execution (C:H/I:H/A:H) through a simple phishing link with no authentication required. The low attack complexity, network reachability, and scope change (OS-level impact from an app-level flaw) mean that any organization running the vulnerable desktop client has a credible initial-access vector sitting on its endpoints. Phishing is the most common initial access technique (MITRE T1566), and this CVE makes every Connect desktop user a viable target. The floor for unauthenticated-remote-RCE-via-click is HIGH.
Crowdsourced verification payload.
Run on each Windows endpoint where Adobe Connect Desktop App may be installed, or push via SCCM/Intune. Requires no elevation — reads registry and file metadata only. Example: powershell -ExecutionPolicy Bypass -File .\Check-CVE-2026-48360.ps1
#Requires -Version 5.1
<# Check-CVE-2026-48360.ps1
Checks whether the Adobe Connect Desktop App is installed and vulnerable to CVE-2026-48360.
Exit codes: 1 = VULNERABLE, 0 = PATCHED, 2 = UNKNOWN (app not found)
#>
$ErrorActionPreference = 'SilentlyContinue'
$found = $false
$vulnerable = $false
$fixedVersion = [version]'2026.9.61'
# Check Uninstall registry keys (both 64-bit and 32-bit)
$regPaths = @(
'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
)
foreach ($path in $regPaths) {
$entries = Get-ItemProperty $path 2>$null | Where-Object {
$_.DisplayName -like '*Adobe Connect*' -and $_.DisplayName -notlike '*Server*'
}
foreach ($entry in $entries) {
$found = $true
$rawVer = $entry.DisplayVersion
Write-Host "[INFO] Found: $($entry.DisplayName) version $rawVer"
try {
$installedVer = [version]($rawVer -replace '[^0-9.]','')
if ($installedVer -lt $fixedVersion) {
$vulnerable = $true
Write-Host "[!!] Version $installedVer is BELOW fixed version $fixedVersion"
} else {
Write-Host "[OK] Version $installedVer is AT or ABOVE fixed version $fixedVersion"
}
} catch {
Write-Host "[WARN] Could not parse version string: $rawVer"
$vulnerable = $true # assume vulnerable if we cannot confirm
}
}
}
# Also check common install paths for the executable
$exePaths = @(
"$env:ProgramFiles\Adobe\Adobe Connect\AdobeConnectApp.exe",
"${env:ProgramFiles(x86)}\Adobe\Adobe Connect\AdobeConnectApp.exe",
"$env:LOCALAPPDATA\Adobe\Adobe Connect\AdobeConnectApp.exe"
)
foreach ($exe in $exePaths) {
if (Test-Path $exe) {
$found = $true
$fileVer = (Get-Item $exe).VersionInfo.ProductVersion
Write-Host "[INFO] Found executable: $exe (ProductVersion: $fileVer)"
try {
$fv = [version]($fileVer -replace '[^0-9.]','')
if ($fv -lt $fixedVersion) {
$vulnerable = $true
Write-Host "[!!] File version $fv is BELOW fixed version $fixedVersion"
} else {
Write-Host "[OK] File version $fv is AT or ABOVE fixed version $fixedVersion"
}
} catch {
Write-Host "[WARN] Could not parse file version: $fileVer"
}
}
}
# Check for URI handler registration
$uriHandler = Get-ItemProperty 'HKCR:\connectpro\shell\open\command' 2>$null
if ($uriHandler) {
Write-Host "[INFO] connectpro:// URI handler registered: $($uriHandler.'(default)')"
}
if (-not $found) {
Write-Host 'UNKNOWN - Adobe Connect Desktop App not detected on this host.'
exit 2
} elseif ($vulnerable) {
Write-Host 'VULNERABLE - Adobe Connect Desktop App is below the fixed version for CVE-2026-48360.'
exit 1
} else {
Write-Host 'PATCHED - Adobe Connect Desktop App is at or above the fixed version.'
exit 0
}