# CVE-2025-32037: Missing authorization in Intel(R) PresentMon

> A network adversary with privileged access can cause a denial of service in Intel PresentMon via improper access control.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-fvgx-8whh-2f9f

## What is CVE-2025-32037?

CVE-2025-32037 is a low-severity missing authorization vulnerability in Intel(R) PresentMon, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control for some Intel(R) PresentMon before version 2.3.1 within Ring 3: User Applications may allow a denial of service. Network adversary with a privileged user combined with a high complexity attack may enable denial of service. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-32037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32037 is a low-severity missing authorization vulnerability in Intel(R) PresentMon, published on 11 Nov 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-32037 in the wild and no public exploit code.

Affected product: Intel(R) PresentMon. 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-32037/ (Markdown: https://insights.sbomify.com/CVE-2025-32037/index.md)
```

## Sources

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

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