VulnerabilityPublished 11 Nov 2025Updated 26 Feb 2026

CVE-2025-30506: Intel Driver and Support Assistant · Escalation of Privilege

Affects Intel Driver and Support AssistantSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 25.2 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.2

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: Active
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Intel Driver and Support Assistant to 25.2.

Affected software

Product	Affected	Fixed in
Intel Driver and Support Assistant	Affected <25.2	Fixed in 25.2

AI-suggested

Update Intel Driver and Support Assistant to version 25.2 or later immediately, as this version addresses the uncontrolled search path vulnerability.
Restrict local user permissions to the minimum necessary to reduce the risk of privilege escalation.
Implement application whitelisting to prevent execution of unauthorized code that could exploit the vulnerability.
Educate users about the risks of executing untrusted files or applications and the importance of cautious behavior to avoid social engineering attacks.
Monitor systems for unusual local activity that could indicate attempts to exploit privilege escalation vulnerabilities.
Employ endpoint detection and response (EDR) tools to detect and block suspicious local privilege escalation attempts.
Regularly audit installed software versions and patch levels to ensure compliance with security policies.
Consider isolating critical systems or limiting installation of non-essential software to reduce attack surface.

Description

Uncontrolled search path for some Intel Driver and Support Assistant before version 25.2 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires active 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.

Impact

The vulnerability allows an authenticated local user to escalate privileges, potentially leading to unauthorized code execution with elevated rights. This can compromise system confidentiality by exposing sensitive data, integrity by allowing unauthorized modification of system files or configurations, and availability by enabling disruptive actions such as service interruptions or system crashes. Although exploitation requires local access and user interaction, the impact on affected systems can be significant, especially in enterprise environments where Intel Driver and Support Assistant is widely deployed. Attackers gaining elevated privileges can bypass security controls, install persistent malware, or move laterally within a network. The medium CVSS score reflects the balance between the attack complexity and the potential damage. Organizations with many users having local access to systems with vulnerable versions are at increased risk. However, the lack of known exploits in the wild and the requirement for active user interaction reduce the immediacy of the threat.

Summary

CVE-2025-30506 is a vulnerability identified in Intel Driver and Support Assistant (IDSA) prior to version 25.2. The root cause is an uncontrolled search path in user-mode components (Ring 3), which can be exploited by a local, authenticated user to escalate privileges. Specifically, the vulnerability allows an adversary with limited privileges to execute code with elevated rights by manipulating the search path used by the IDSA application. Exploitation requires a high level of attack complexity and active user interaction, such as tricking the user into running malicious code or opening a crafted file. The vulnerability affects confidentiality, integrity, and availability of the system, potentially allowing unauthorized access or modification of sensitive data and disruption of system operations. The CVSS 4.0 base score is 5.4, reflecting a medium severity rating. The attack vector is local (AV:L), with high attack complexity (AC:H), no attack vector (AT:N), low privileges required (PR:L), and user interaction needed (UI:A). The vulnerability does not require network access and is limited to local exploitation. No known public exploits or widespread attacks have been reported to date. The vulnerability is specific to Intel Driver and Support Assistant software, which is commonly installed on systems with Intel hardware to facilitate driver updates and system diagnostics.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01361.html (opens in a new tab)

Community reviews

Loading reviews…