CVE-2026-5064 · Potential security vulnerabilities have been identified in the HP O…

01 · The Real Story

Someone left a spare key under the doormat, but the door is inside your house and only opens one room

CVE-2026-5064 is an uncontrolled search path element (CWE-427) in HP One Agent, the unified telemetry and fleet-management agent pre-installed on HP commercial and consumer PCs. Versions prior to 1.3.214.7339 run a scheduled task or service process as NT AUTHORITY\SYSTEM that resolves an executable (likely powershell.exe or a helper binary) via the standard Windows search order rather than an absolute path. If an attacker can place a malicious binary in a writable directory that appears earlier in the system PATH environment variable, the SYSTEM-level process loads it — instant local privilege escalation. The fix ships as HP Privacy Settings 1.5.21.0 or later (bundling HP One Agent ≥ 1.3.214.7339) via the Microsoft Store.

No vendor CVSS 3.1 baseline exists; HP published only a CVSS 4.0 score of 8.5 (HIGH) with vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. That 8.5 is generous. It reflects the *theoretical* ease of exploitation once prerequisites are met, but ignores that the attacker must already have local interactive access AND a writable directory prepended in the system PATH — a condition that is far from universal. Enterprise workstations managed by SCCM/Intune rarely have user-writable PATH entries by default. The blast radius is a single workstation, not fleet-scale infrastructure. A MEDIUM assessment at 5.5 better reflects the real-world risk.

"Local-only LPE via PATH hijacking on HP endpoint bloatware; workstation blast radius, no wild exploitation."

02 · The Attack Path

4 steps from start to impact.

STEP 01

Obtain local low-privilege access on an HP PC

The attacker needs an interactive or scripted session on a Windows host running HP One Agent < 1.3.214.7339. This is typically achieved via phishing, stolen credentials, or lateral movement from an already-compromised host. No remote vector exists for this CVE itself.

Conditions required:

Low-privilege local user account on a target HP PC
HP One Agent < 1.3.214.7339 installed (pre-loaded on HP commercial PCs)

Where this breaks in practice:

Requires prior compromise — this is a post-initial-access technique, not an entry vector
Only HP-branded PCs ship with HP One Agent; Dell, Lenovo, etc. are unaffected

Detection/coverage: EDR agents monitoring process creation under SYSTEM context from unusual PATH directories will flag this. Sysmon Event ID 1 with ParentImage matching CompatTelRunner.exe or HP One Agent service spawning unexpected children.

STEP 02

Identify or create a writable directory in system PATH

The attacker enumerates the system PATH environment variable looking for directories where the low-privilege user has write access AND that appear before C:\Windows\System32 or the legitimate binary location. Common culprits include Python, Node.js, Conda, or poorly configured application directories. If no writable PATH entry exists, the attack fails unless the attacker can modify PATH (which typically requires admin privileges, creating a chicken-and-egg problem).

Conditions required:

At least one user-writable directory exists in the system PATH before the legitimate executable location

Where this breaks in practice:

Well-managed enterprise images (SCCM/Intune baselines) rarely have user-writable PATH entries
Default Windows installations do not have this condition
Modifying the system PATH itself requires administrative privileges

Detection/coverage: Audit tools like AccessChk or custom PowerShell scripts can enumerate writable PATH directories. CIS Benchmark checks flag this misconfiguration.

STEP 03

Drop malicious binary in writable PATH directory

The attacker places a malicious executable (e.g., powershell.exe or whichever binary HP One Agent resolves via search order) into the writable PATH directory. The binary is a payload — typically a reverse shell, Cobalt Strike beacon, or simple cmd.exe wrapper that adds the attacker to local administrators. File creation in a PATH directory is a well-known indicator of compromise.

Conditions required:

Write access to the identified PATH directory
Knowledge of the binary name HP One Agent resolves

Where this breaks in practice:

Application whitelisting (WDAC/AppLocker) blocks execution of unsigned binaries from non-standard locations
EDR file-write monitoring on PATH directories catches this in most mature environments

Detection/coverage: WDAC/AppLocker audit mode logs, EDR file creation alerts in PATH directories, AMSI scanning of dropped executables.

STEP 04

Wait for or trigger scheduled task execution

The HP One Agent service or scheduled task runs periodically under SYSTEM context. When it executes, it resolves the binary name via Windows search order, finds the attacker's malicious binary first, and executes it as NT AUTHORITY\SYSTEM. The attacker now has full SYSTEM privileges on the single workstation.

Conditions required:

HP One Agent scheduled task or service must run (it runs automatically on a schedule)

Where this breaks in practice:

If the agent has been disabled or uninstalled by IT policy, the task never fires
Time-to-exploitation depends on the task schedule — not instant

Detection/coverage: Process creation events showing SYSTEM-level execution from a non-standard directory. Sysmon, CrowdStrike, Defender for Endpoint all detect this pattern reliably.

03 · Intelligence Metadata

The supporting signals.

In-the-Wild Exploitation	None observed. Not listed on CISA KEV. No campaigns or threat actor usage reported as of September 2026.
Proof-of-Concept	No public PoC specific to CVE-2026-5064. The underlying technique (search order hijacking via writable PATH) is well-documented generically — see itm4n's MareBackup research for the general Windows pattern. No weaponized exploit exists.
EPSS Score	0.00114 (1.6th percentile) — bottom of the probability distribution, indicating extremely low predicted exploitation likelihood.
KEV Status	Not listed. No CISA deadline.
CVSS Vector	CVSS 4.0: `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` — 8.5 HIGH. Local attack vector, low privileges, no user interaction. No CVSS 3.1 score published by NVD (status: Awaiting Analysis).
Affected Versions	HP One Agent < 1.3.214.7339 on Windows. Pre-installed on HP commercial and consumer PCs.
Fixed Version	HP One Agent ≥ 1.3.214.7339, delivered via HP Privacy Settings 1.5.21.0+ from the Microsoft Store.
Scanning / Exposure	Not applicable — this is a local-only vulnerability on endpoint software. No Shodan/Censys/GreyNoise exposure data. Endpoint vulnerability scanners (Qualys, Tenable, Rapid7) should detect via agent-based version checks of HP One Agent.
Disclosure Date	2026-06-15 (HP advisory HPSBHF04060).
Credited Researcher	Not publicly disclosed in the HP advisory.

04 · The Call

noisgate verdict.

Final Verdict

= UNCHANGED to MEDIUM (5.5/10)

The single most decisive factor is the compounding local prerequisites: the attacker must already hold local access on an HP workstation AND that workstation must have a user-writable directory prepended in the system PATH — a misconfiguration that well-managed enterprise images do not exhibit by default. The blast radius is a single workstation, not fleet-scale infrastructure, and the component occupies no high-value deployment role.

HIGH Vulnerability mechanism and affected version range

HIGH No in-the-wild exploitation or public PoC

MEDIUM Prevalence of writable PATH directories in enterprise HP fleets

Why this verdict

Local access prerequisite: AV:L means the attacker is already post-initial-access. This is not an entry vector — it is a privilege escalation step that compounds with a prior compromise.
PATH misconfiguration gate: The attack only works when a user-writable directory exists in the system PATH before the legitimate binary location. Default Windows and managed enterprise images (CIS-hardened, Intune-deployed) do not exhibit this. This narrows the exploitable population significantly.
Workstation-only blast radius: HP One Agent runs on HP PCs — workstations and laptops. Compromising SYSTEM on one workstation does not cascade to domain controllers, hypervisors, or fleet infrastructure. The impact is contained to a single host.
Role multiplier: HP One Agent is an endpoint telemetry/management agent on workstations (low-value role). It is not deployed on domain controllers, hypervisors, backup servers, or other high-value infrastructure. The chain ends at single-host SYSTEM — no fleet-scale, identity-scale, or supply-chain-scale outcome. The high-value role floor does not apply.
No exploitation signal: EPSS 0.00114 (1.6th percentile), no KEV listing, no public PoC, no observed campaigns. The threat intelligence picture is uniformly cold.

Why not higher?

Elevating to HIGH would require either active exploitation evidence, a broader blast radius, or a deployment role where SYSTEM on the host implies fleet-scale impact. None of these conditions exist. HP One Agent is workstation bloatware, and the PATH writable-directory prerequisite meaningfully narrows the exploitable population beyond what a generic 'local access' chain would imply.

Why not lower?

Dropping to LOW would understate the risk for the subset of HP fleets where writable PATH directories exist (e.g., developer workstations with Python/Node.js/Conda in PATH). In those environments, the chain is trivial and reliable — local user → SYSTEM with no user interaction. HP's large commercial PC market share means many enterprises have thousands of potentially affected endpoints, even if only a fraction are exploitable. The LPE-to-SYSTEM outcome is still meaningful for lateral movement and persistence.

05 · Compensating Control

What to do — in priority order.

Audit and harden system PATH on HP workstations — Run a fleet-wide scan for user-writable directories in the system PATH environment variable. Remove or re-ACL any writable entries. This eliminates the prerequisite for exploitation entirely. No noisgate mitigation SLA applies for MEDIUM — go straight to the 365-day remediation window for the patch itself.
Deploy application whitelisting (WDAC/AppLocker) — Enforce a policy that blocks execution of unsigned or unknown binaries from non-standard directories. This prevents the malicious binary from executing even if placed in a writable PATH directory. Effective as a defense-in-depth measure.
Update HP One Agent via Microsoft Store — Push HP Privacy Settings ≥ 1.5.21.0 (which bundles HP One Agent ≥ 1.3.214.7339) via Microsoft Store for Business or Intune. This is the definitive remediation within the noisgate remediation SLA of 365 days.
Consider removing HP One Agent if unused — If your organization does not use HP Workforce Experience Platform or HP Proactive Insights, uninstall HP One Agent entirely. Reducing attack surface by removing unnecessary vendor bloatware is the strongest control.

What doesn't work

Network segmentation / firewall rules — This is a local privilege escalation; network controls have no bearing on the attack path.
MFA / conditional access — The vulnerability exploits a local service, not an authentication flow. MFA does not prevent SYSTEM escalation.
Endpoint Detection and Response (EDR) as sole mitigation — While EDR will likely *detect* the exploitation pattern, relying on detection alone without hardening PATH or patching leaves a window where the LPE succeeds before response. EDR is a detection layer, not a prevention control for this specific chain.

06 · Verification

Crowdsourced verification payload.

Run this script on each HP workstation (or push via SCCM/Intune) as any user. No admin privileges required. Example: powershell -ExecutionPolicy Bypass -File Check-CVE-2026-5064.ps1

noisgate-verify.ps1

POWERSHELLREAD-ONLYSAFE

#Requires -Version 5.1
<# Check-CVE-2026-5064.ps1
   Checks whether HP One Agent is installed and vulnerable to CVE-2026-5064.
   Output: VULNERABLE / PATCHED / UNKNOWN
   Exit codes: 1 = VULNERABLE, 0 = PATCHED, 2 = UNKNOWN
#>

$ErrorActionPreference = 'SilentlyContinue'
$found = $false
$vulnerable = $false

# Check via registry (HP One Agent / HP Privacy Settings)
$regPaths = @(
    'HKLM:\SOFTWARE\HP\HP One Agent',
    'HKLM:\SOFTWARE\WOW6432Node\HP\HP One Agent',
    'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
    'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
)

foreach ($path in $regPaths) {
    $entries = Get-ItemProperty -Path $path -ErrorAction SilentlyContinue | Where-Object { $_.DisplayName -like '*HP One Agent*' -or $_.DisplayName -like '*HP Privacy*' }
    foreach ($entry in $entries) {
        $found = $true
        $ver = $entry.DisplayVersion
        if ($ver) {
            try {
                $parsed = [version]$ver
                $fixedVer = [version]'1.3.214.7339'
                if ($parsed -lt $fixedVer) {
                    $vulnerable = $true
                    Write-Host "VULNERABLE - HP One Agent version $ver is below fixed version 1.3.214.7339"
                } else {
                    Write-Host "PATCHED - HP One Agent version $ver meets or exceeds fixed version 1.3.214.7339"
                }
            } catch {
                Write-Host "UNKNOWN - Could not parse version: $ver"
                exit 2
            }
        }
    }
}

# Fallback: check for HP One Agent files
if (-not $found) {
    $agentPaths = @(
        "$env:ProgramFiles\HP\HP One Agent",
        "${env:ProgramFiles(x86)}\HP\HP One Agent",
        "$env:ProgramData\HP\HP One Agent"
    )
    foreach ($p in $agentPaths) {
        if (Test-Path $p) {
            $found = $true
            $dll = Get-ChildItem -Path $p -Filter '*.exe' -Recurse | Select-Object -First 1
            if ($dll) {
                $fileVer = $dll.VersionInfo.FileVersion
                if ($fileVer) {
                    try {
                        $parsed = [version]($fileVer -replace '[^0-9.]','')
                        $fixedVer = [version]'1.3.214.7339'
                        if ($parsed -lt $fixedVer) {
                            $vulnerable = $true
                            Write-Host "VULNERABLE - HP One Agent file version $fileVer is below 1.3.214.7339"
                        } else {
                            Write-Host "PATCHED - HP One Agent file version $fileVer meets or exceeds 1.3.214.7339"
                        }
                    } catch {
                        Write-Host "UNKNOWN - Could not parse file version: $fileVer"
                        exit 2
                    }
                }
            }
        }
    }
}

if (-not $found) {
    Write-Host "UNKNOWN - HP One Agent not detected on this system (may not be an HP PC)"
    exit 2
}

if ($vulnerable) { exit 1 } else { exit 0 }

07 · Bottom Line

If you remember one thing.

TL;DR

MEDIUM at 5.5 — no mitigation SLA applies. HP One Agent is endpoint bloatware with a local-only privilege escalation that requires a writable PATH directory. If your fleet is HP-heavy, add CVE-2026-5064 to your standard remediation backlog under the noisgate remediation SLA of 365 days. Push the update (HP Privacy Settings ≥ 1.5.21.0 via Microsoft Store for Business) through your normal patching cadence — there is no noisgate mitigation SLA for MEDIUM, so go straight to the remediation window. If you want to derisk faster, audit system PATH entries fleet-wide for user-writable directories and re-ACL them; this eliminates the prerequisite entirely and is good hygiene regardless. If your organization doesn't use HP Proactive Insights or Workforce Experience Platform, consider uninstalling HP One Agent outright to shrink your attack surface. No active exploitation or PoC exists — this is not a fire drill.

Sources

Peer Review

What defenders are saying.

Submit a review attribution: handle + country only

0 flags selected · stored anonymously

Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.