Answer in brief
CVE-2025-3935 records a High severity vulnerability in ScreenConnect Exposure to ASP.NET ViewState Code Injection. The current sources mark it as known exploited. The current feed maps ConnectWise/ScreenConnect (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ConnectWise/ScreenConnect (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ConnectWise/ScreenConnectgeneric | <25.2.3 | Not reported |
Published upstream
Apr 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Feb 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Jun 2, 2025
Evidence: source:kev:kev:kev:recordScreenConnect 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 on the server. The risk does not originate from a vulnerability introduced by ScreenConnect, but from platform level behavior. This had no direct impact to ScreenConnect Client. ScreenConnect 2025.4 patch disables ViewState and removes any dependency on it.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-3935 records a High severity vulnerability in ScreenConnect Exposure to ASP.NET ViewState Code Injection. The current sources mark it as known exploited. The current feed maps ConnectWise/ScreenConnect (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ConnectWise/ScreenConnect (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ConnectWise/ScreenConnectgeneric | <25.2.3 | Not reported |
Published upstream
Apr 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Feb 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Jun 2, 2025
Evidence: source:kev:kev:kev:recordScreenConnect 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 on the server. The risk does not originate from a vulnerability introduced by ScreenConnect, but from platform level behavior. This had no direct impact to ScreenConnect Client. ScreenConnect 2025.4 patch disables ViewState and removes any dependency on it.
Quoted source text, attributed separately from HOL analysis.