CVE-2025-52095: PDQ Smart Deploy · Insufficiently Protected Credentials
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Immediately inventory all systems running PDQ Smart Deploy, focusing on version 3.0.2040 or earlier.
- Restrict network access to PDQ Smart Deploy management interfaces using network segmentation and firewall rules, limiting exposure to trusted administrators only.
- Monitor network traffic and system logs for unusual activity related to SDCommon.dll or credential handling processes.
- Employ endpoint detection and response (EDR) solutions to detect anomalous privilege escalation attempts.
- Enforce the principle of least privilege on accounts managing PDQ Smart Deploy to minimize potential damage.
- Until an official patch is released, consider temporarily disabling or isolating PDQ Smart Deploy deployments if feasible.
- Stay updated with vendor advisories and apply patches immediately upon release.
- Conduct internal security awareness to recognize potential exploitation indicators and report suspicious behavior promptly.
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