SYSTEM code execution via trusted temporary package files
Published Mar 5, 2025 · Updated Nov 3, 2025
Privilege escalation in Vasion Print Application before 20.0.2368 and Virtual Appliance Host before 22.0.933 lets local users run code as SYSTEM. The Windows client installs printer drivers as NT AUTHORITY\SYSTEM but blindly trusts temporary package files in the user-writable C:\Windows\Temp\data directory. A low-privileged local user can replace those files or redirect the directory with a junction during driver installation, causing attacker-controlled code to run as SYSTEM.
Summary
What happened
Privilege escalation in Vasion Print Application before 20.0.2368 and Virtual Appliance Host before 22.0.933 lets local users run code as SYSTEM. The Windows client installs printer drivers as NT AUTHORITY\SYSTEM but blindly trusts temporary package files in the user-writable C:\Windows\Temp\data directory. A low-privileged local user can replace those files or redirect the directory with a junction during driver installation, causing attacker-controlled code to run as SYSTEM.
The record
- CVE
- CVE-2025-27644
- Published
- Mar 5, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Windows temporary-package replacement and junction proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo