CVE-2026-50109

Summary

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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
Reach?/20Unknown. No tracked technology or package matched
Severity8.3/10CVSS 8.3
No patch0/5No signal

What would change the score

Would score about 70 if added to CISA KEV
Would score about 65 if CISA's SSVC rates exploitation active
Would score about 30 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

Upgrade to a fixed version: commit #d626ea0 on April 30th of 2026 or later.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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.

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.

Timeline

Nov 10, 2026, 4:31 PM UTCCVE published
Nov 10, 2026, 4:36 PM UTCFirst seen by cve.now

Affected versions

n/a Intel(R) Performance Counter Monitor (Intel(R) PCM)
Version range not reported

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Link
intel.com · content/www/us/en/security-center/advisory/intel-sa-01528.html

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-50109
Record
NVD · CVE-2026-50109

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-50109

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: cve.now feed data

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: intel.com

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: intel.com

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: intel.com

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