# CVE-2025-10576: Sound Research SECOMNService Escalation of Privilege

> Attackers can escalate privileges via the Sound Research SECOMN64 audio driver on HP PCs, requiring updated audio packages.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 15 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-wj82-cv5p-ff54

## What is CVE-2025-10576?

CVE-2025-10576 is a high-severity vulnerability in HP, Inc. Sound Research, published on 15 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Potential vulnerabilities have been identified in the audio package for certain HP PC products using the Sound Research SECOMN64 driver, which might allow escalation of privilege. HP is releasing updated audio packages to mitigate the potential vulnerabilities.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-10576 being exploited?

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

Public exploit code:

- HP Sound Research SECOMNService Escalation of Privilege (github_poc): https://github.com/R41N3RZUF477/CVE-2025-10576

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10576 is a high-severity vulnerability in HP, Inc. Sound Research, published on 15 Oct 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-10576 in the wild and no public exploit code.

Affected product: HP, Inc. Sound Research. 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-10576/ (Markdown: https://insights.sbomify.com/CVE-2025-10576/index.md)
```

## Sources

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

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