← Back to Feed CACHED · 2026-10-28 12:13:02 · CACHE_KEY CVE-2026-48360
CVE-2026-48360 · CWE-94 · Disclosed 2026-10-27

Adobe Connect Desktop App client-side code injection via crafted URL

ASSESSED — NOISGATE
Vendor
—
—
—
Reassessed
—
—
—
Verdict: —
Do you agree?
01 · The Real Story

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.

"Client-side RCE via crafted URL in a niche meeting app — painful but not fleet-scale."
02 · The Attack Path

4 steps from start to impact.

STEP 01

Deliver malicious URL to victim

The attacker crafts a URL that targets the Adobe Connect Desktop App's input-processing path — either a custom URI scheme (e.g., 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.
Conditions required:
  • Victim has an email address or browses attacker-influenced content
  • Attacker can craft a URL that the Connect desktop app will process
Where this breaks in practice:
  • 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)
Detection/coverage: Email security gateways (Proofpoint, Mimecast, Microsoft Defender for Office 365) can flag or detonate URLs with unusual URI schemes. Proxy logs will show the initial HTTP request if the link goes through a web redirect.
STEP 02

Adobe Connect desktop app processes malicious input

When the victim clicks the link (or the browser dispatches to the app), the Adobe Connect Desktop Application parses the attacker-controlled input. Because the app embeds a Chromium engine (upgraded to v141 in the 2026.3 release cycle), the injected payload reaches a code-generation path — likely a JavaScript bridge, a custom protocol handler, or a dynamic content renderer — where it is incorporated into executable code without sanitization.
Conditions required:
  • 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)
Where this breaks in practice:
  • 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
Detection/coverage: EDR telemetry should show the Adobe Connect process spawning or loading unusual child processes. Sysmon Event ID 1 (Process Create) with parent AdobeConnectApp.exe or equivalent is a strong signal.
STEP 03

Code injection achieves OS-level execution

The injected code escapes the application's rendering context (Scope:Changed) and executes arbitrary commands with the privileges of the logged-in user. On Windows this means the attacker gets a shell as the desktop user; on macOS/Android the equivalent user-context execution applies. This is the terminal impact step — the attacker now has a foothold on the endpoint.
Conditions required:
  • Steps 1 and 2 succeeded
  • No application-level sandbox or code-signing enforcement blocks the injected payload
Where this breaks in practice:
  • 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
Detection/coverage: EDR behavioral rules (CrowdStrike, SentinelOne, MDE) should flag a conferencing app executing cmd.exe, powershell.exe, bash, or making anomalous network connections. AMSI on Windows can inspect script content before execution.
STEP 04

Post-exploitation and lateral movement

With code execution on the endpoint, the attacker can harvest credentials (browser session tokens, cached credentials, Kerberos tickets), establish C2, and pivot laterally. The blast radius depends entirely on the compromised user's role — a help-desk admin yields more than a contractor on a locked-down laptop. This step is outside the CVE's scope but determines the real-world impact.
Conditions required:
  • Step 3 succeeded
  • Endpoint has accessible credentials or network paths to higher-value targets
Where this breaks in practice:
  • 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.)
Detection/coverage: Identity-threat detection (Microsoft Defender for Identity, CrowdStrike Falcon Identity) flags anomalous authentication patterns. SIEM correlation on unusual process → network flows from the compromised host.
03 · Compensating Control

1
HIGH 8.0→IGNORE 0.0
SEVERITY REDUCED
Patch to fixed desktop app versions immediately — Deploy Windows 2026.9.61, Mac Silicon 2026.10.66, Mac Intel 2026.10.170, and Android 4.5. This is the definitive fix. Per the noisgate mitigation SLA for HIGH, deploy compensating controls within 30 days; per the remediation SLA, complete patching within 180 days. Given the simplicity of the attack chain, prioritize patching over mitigations.
2
HIGH 8.0→LOW 3.0
SEVERITY REDUCED
Block or quarantine Adobe Connect custom URI schemes at the endpoint — Use Group Policy, Intune, or MDM to deregister or block the 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.
3
HIGH 8.0→MEDIUM 5.5
SEVERITY REDUCED
Enforce email gateway URL detonation and rewriting — Ensure your email security gateway (Proofpoint, Mimecast, MDE for O365) detonates URLs in a sandbox and rewrites links to pass through a safe-link proxy. This degrades Step 1 by catching or neutering the malicious URL before it reaches the user's inbox. Most mature email gateways already do this; verify the policy covers custom URI schemes.
4
HIGH 8.0→MEDIUM 5.0
SEVERITY REDUCED
Configure EDR behavioral rules for anomalous child processes from meeting apps — Create or verify EDR detection rules that alert on 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.
5
HIGH 8.0→IGNORE 0.0
SEVERITY REDUCED
Uninstall the desktop app where browser access suffices — If your Adobe Connect deployment can function with browser-only access (most can), remove the desktop application entirely from endpoints that don't strictly need it. This eliminates the attack surface completely for those hosts. Coordinate with your meeting/training team to confirm browser compatibility.
What doesn't work
  • 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.
04 · Intelligence Metadata

The supporting signals.

In-the-wild exploitationNone 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-conceptNo public PoC. No repositories on GitHub named after CVE-2026-48360. Not indexed on pocindex.io, Exploit-DB, or Metasploit. No Nuclei template available.
EPSSNot yet scored. FIRST EPSS API returns empty data for this CVE (published 2026-10-27, likely too new for the daily model run).
KEV statusNot listed in CISA Known Exploited Vulnerabilities catalog as of 2026-10-28.
CVSS vectorCVSS: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 versionsDesktop App: Windows ≤2026.8.51, Mac Silicon ≤2026.08.45, Mac Intel ≤2026.01.39. Android Mobile App ≤4.4.
Fixed versionsWindows 2026.9.61, Mac Silicon 2026.10.66, Mac Intel 2026.10.170, Android 4.5. Bulletin APSB26-182, priority rating 2.
Exposure dataNo 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 date2026-10-27 (CVE reserved 2026-05-21). NVD status: 'Received' — analysis pending.
Credited researcherCredited to 'al' per Adobe's APSB26-182 bulletin.

Sources.

  1. Adobe APSB26-182 Advisory (via SecurityOnline roundup)
  2. OffSeq Radar — CVE-2026-48360 Threat Intelligence
  3. Strix AI — CVE-2026-48360 Detail
  4. TheHackerWire — CVE-2026-48360 Analysis
  5. Adobe Connect Desktop App 2026.3 Release Notes
  6. Adobe Connect Security Bulletin APSB26-150 (September 2026)
  7. FIRST EPSS API — CVE-2026-48360 (no data yet)
05 · The Call

Final Verdict
↓ DOWNGRADED to HIGH (8.0/10)

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.

06 · Verification

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

noisgate-verify.ps1
POWERSHELLREAD-ONLYSAFE
#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
}