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 on the server side, preventing encrypted values from being transmitted to or rendered by client-side components.
References
Configurations
History
16 Jan 2026, 19:10
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:connectwise:screenconnect:*:*:*:*:*:*:*:* | |
| First Time |
Connectwise screenconnect
Connectwise |
|
| References | () https://www.connectwise.com/company/trust/security-bulletins/2025-12-18-screenconnect-certificate-signing-extension-update - Vendor Advisory |
18 Dec 2025, 16:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-12-18 16:15
Updated : 2026-01-16 19:10
NVD link : CVE-2025-14823
Mitre link : CVE-2025-14823
CVE.ORG link : CVE-2025-14823
JSON object : View
Products Affected
connectwise
- screenconnect
CWE
CWE-201
Insertion of Sensitive Information Into Sent Data
