本ページは connectwise screenconnect に影響する公開済み CVE（NVD の CPE 経由で関連付け）を列挙します。各行に深刻度指標・概要・公開日が含まれます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2025-14823 | In deployments using the ScreenConnect™ Certificate Signing Extension, encrypted configuration values including an Azure Key Vault-related key, could be returned to unauthenticated users through a client-facing endpoint under certain conditions. The values remained encrypted and securely stored at rest; however, an encrypted representation could be exposed in client responses. Updating the Certificate Signing Extension to version 1.0.12 or higher ensures configuration handling occurs exclusively | 7d616e1a-3288-43b1-a0dd-0a65d3e70a49 | 5.3 | 0.02% | 2025-12-18 | 2026-01-16 |
| CVE-2025-14265 | In versions of ScreenConnect™ prior to 25.8, server-side validation and integrity checks within the extension subsystem could allow the installation and execution of untrusted or arbitrary extensions by authorized or administrative users. Abuse of this behavior could result in the execution of custom code on the server or unauthorized access to application configuration data. This issue affects only the ScreenConnect server component; host and guest clients are not impacted. ScreenConnect 25.8 i | 7d616e1a-3288-43b1-a0dd-0a65d3e70a49 | 9.1 | 0.05% | 2025-12-11 | 2026-01-16 |
| CVE-2025-3935 KEV | ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack. ASP.NET Web Forms use ViewState to preserve page and control state, with data encoded using Base64 protected by machine keys. It is important to note that to obtain these machine keys, privileged system level access must be obtained. If these machine keys are compromised, attackers could create and send a malicious ViewState to the website, potentially leading to remote code execution | 7d616e1a-3288-43b1-a0dd-0a65d3e70a49 | 8.1 | 6.15% | 2025-04-25 | 2025-10-24 |
| CVE-2024-1709 KEV | ConnectWise ScreenConnect 23.9.7 and prior are affected by an Authentication Bypass Using an Alternate Path or Channel vulnerability, which may allow an attacker direct access to confidential information or critical systems. | 9119a7d8-5eab-497f-8521-727c672e3725 | 10.0 | 94.35% | 2024-02-21 | 2026-02-26 |
| CVE-2024-1708 KEV | ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an attacker the ability to execute remote code or directly impact confidential data or critical systems. | 9119a7d8-5eab-497f-8521-727c672e3725 | 8.4 | 84.81% | 2024-02-21 | 2026-04-28 |
| CVE-2023-47257 | ConnectWise ScreenConnect through 23.8.4 allows man-in-the-middle attackers to achieve remote code execution via crafted messages. | [email protected] | 8.1 | 6.72% | 2024-02-01 | 2025-05-07 |
| CVE-2023-47256 | ConnectWise ScreenConnect through 23.8.4 allows local users to connect to arbitrary relay servers via implicit trust of proxy settings | [email protected] | 5.5 | 0.05% | 2024-02-01 | 2025-06-17 |
| CVE-2022-36781 | ConnectWise ScreenConnect versions 22.6 and below contained a flaw allowing potential brute force attacks on custom access tokens due to inadequate rate-limiting controls in the default configuration. Attackers could exploit this vulnerability to gain unauthorized access by repeatedly attempting access code combinations. ConnectWise has addressed this issue in later versions by implementing rate-limiting controls as a preventive measure against brute force attacks. | [email protected] | 5.3 | 0.47% | 2022-09-28 | 2024-11-21 |