# CVE-2026-7539: HP Dock Accessory WMI Provider Installer Security Update

> An attacker can escalate privileges and execute arbitrary code via the HP Dock Accessory WMI Provider installer on HP docking stations.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-fcm3-pjp2-xx9r

## What is CVE-2026-7539?

CVE-2026-7539 is a high-severity vulnerability in HP Dock Accessory, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A potential security vulnerability has been identified in the HP Accessory WMI Provider installer for some HP Docking Stations, which might allow escalation of privilege and/or arbitrary code execution. HP is releasing software updates to mitigate the potential vulnerability.

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

## Which versions are affected by CVE-2026-7539?


## How do I fix CVE-2026-7539?

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

## Is CVE-2026-7539 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7539 and fix it if it is affected.

What it is: CVE-2026-7539 is a high-severity vulnerability in HP Dock Accessory, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7539 in the wild and no public exploit code.

Affected product: HP Dock Accessory. 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-2026-7539/ (Markdown: https://insights.sbomify.com/CVE-2026-7539/index.md)
```

## Sources

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

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