# CVE-2025-52094: Privilege escalation in n/a

> A local attacker can execute arbitrary code with elevated privileges due to insecure permissions in the PDQ Smart Deploy registry component.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-qwcj-864r-p95m

## What is CVE-2025-52094?

CVE-2025-52094 is a high-severity vulnerability in n/a, published on 22 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure Permissions vulnerability in PDQ Smart Deploy V.3.0.2040 allows a local attacker to execute arbtirary code via the \HKLM\SYSTEM\Setup\SmartDeploy component

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-52094?

It affects 1 product.


Products: Pdq Smart Deploy.

## How do I fix CVE-2025-52094?

No fix has been published for CVE-2025-52094 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52094 being exploited?

There is no known exploitation of CVE-2025-52094 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-52095](https://insights.sbomify.com/CVE-2025-52095/): Weak cryptography in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52094 and fix it if it is affected.

What it is: CVE-2025-52094 is a high-severity vulnerability in n/a, published on 22 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52094 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52094/ (Markdown: https://insights.sbomify.com/CVE-2025-52094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52094
- OSV: https://osv.dev/vulnerability/CVE-2025-52094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52094/
Summaries are generated and may contain mistakes; the official description above is the record.