CVE-2025-52095 Details
Description
An issue in PDQ Smart Deploy V.3.0.2040 allows an attacker to escalate privileges via the Credential encryption routines in SDCommon.dll
A privilege escalation vulnerability has been identified in PDQ Smart Deploy version 3.0.2040. The issue arises from the credential encryption routines in the SDCommon.dll file, which use static, hardcoded keys. This flaw allows low-privileged users to decrypt sensitive credentials, such as those for Local Administrator or Active Directory accounts, from the registry of managed devices or from deployment files on the server.
Users can upgrade to PDQ Smart Deploy version 3.0.2046, which addresses the vulnerability by implementing a new encryption method that eliminates the use of static keys.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 26, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://specterops.io/blog/2025/08/12/hklmsystemsetupsmartdeploy-the-static-keys-to-abusing-pdq-smartdeploy/ | [email protected] | ExploitThird Party Advisory |
| https://www.pdq.com/ | [email protected] | Product |
| https://www.pdq.com/products/smartdeploy/ | [email protected] | Product |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-522 | Insufficiently Protected Credentials | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| pdq smart deploy | < 3.0.2046 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 27, 2026 | Initial Analysis | [email protected] |
| Aug 26, 2025 | CVE Modified | CISA-ADP |
| Aug 22, 2025 | New CVE Received | [email protected] |