# CVE-2025-61969: Privilege escalation in AMD µProf

> A local attacker can exploit incorrect permissions in AMD µProf to escalate privileges and execute arbitrary code.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-r36r-8jrx-92cq

## What is CVE-2025-61969?

CVE-2025-61969 is a high-severity vulnerability in AMD µProf, published on 11 Feb 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

Incorrect permission assignment in AMD µProf may allow a local user-privileged attacker to achieve privilege escalation, potentially resulting in arbitrary code execution.

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

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


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

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

## Is CVE-2025-61969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61969 is a high-severity vulnerability in AMD µProf, published on 11 Feb 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-2025-61969 in the wild and no public exploit code.

Affected product: AMD µProf. 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-61969/ (Markdown: https://insights.sbomify.com/CVE-2025-61969/index.md)
```

## Sources

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

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