Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Impact | CVSS 7.8 (High) with AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates significant real-world risk: local attack vector, low complexity, requires low privileges (standard user), no user interaction, impacts confidentiality, integrity, and availability. The S:U (Scope Unchanged) component limits domain escape but does not reduce severity of local privilege escalation. EPSS probability (if available) should be evaluated; exploitation likelihood is elevated because: (1) AC:L means no special conditions needed; (2) PR:L suggests any authenticated local user can trigger; (3) link-following bugs are well-understood attack patterns with existing research. KEV/CISA inclusion would indicate active exploitation. POC availability would elevate immediate risk. This is NOT a low-real-risk scenario—link-following vulnerabilities in privileged processes are reliably exploitable. Compare against SSVC: exploitation is likely probable/active (depends on KEV status), automatable (no user interaction), technical impact is total (privilege escalation to SYSTEM), making this a critical patch priority regardless of EPSS. |
| Exploit ScenarioDerived | An authorized standard user on a Windows system crafts a malicious MSI package or intercepts a legitimate MSI installation. During MSI processing by msiexec.exe (executing with elevated privileges for system-wide install), the attacker exploits the link-following vulnerability by creating a symbolic link or NTFS junction in the installer's working directory (e.g., %TEMP% or installation staging location) that points to a sensitive system file or directory (e.g., C:\Windows\System32\config\SAM, a privileged registry hive, or a system executable). When Windows Installer's file operations follow the unvalidated link to read, write, or execute the target, the attacker gains the ability to: (a) read sensitive files (SAM dump leading to password cracking), (b) write to system locations (plant backdoors or modify critical binaries), or (c) execute arbitrary code in SYSTEM context (privilege escalation). AC:L means the attacker requires no special timing—the TOCTOU window is naturally present during MSI processing. No user interaction (UI:N) is required beyond the initial MSI invocation. POC would demonstrate link creation and exploitation steps; if one exists and is public, real-world risk is significantly elevated. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 14, 2026
Privilege escalation vulnerability in Windows Installer that exploits improper symlink/junction handling (CWE-59: link following) to allow an authorized local attacker to elevate privileges without user interaction. With a CVSS score of 7.8 and CVSS vector indicating local attack vector with low complexity and no user interaction required, this vulnerability affects Windows Installer across multiple versions. Real-world risk depends on KEV/CISA status and EPSS probability, which should be cross-referenced against active exploitation reports and POC availability.
RemediationAI
- PATCH: Apply Microsoft security updates addressing CVE-2025-33075 via Windows Update or Microsoft Update Catalog (KB article TBD—check Microsoft Security Response Center). 2. PRIORITIZE: Treat as high-priority patching given privilege escalation severity. 3. WORKAROUNDS (if patch delayed): (a) Restrict MSI installation privileges via Group Policy ('Disable Windows Installer' or 'Always install with elevated privileges' policies—though caveat: these may break legitimate installs); (b) Monitor %TEMP% and installation directories for suspicious symlink/junction creation (detection evasion technique); (c) Require administrative approval for all MSI installations (increases friction but reduces attack surface). 4. DETECTION: Implement file system monitoring for symlink/junction creation in installer working directories and temporary paths; correlate with MSI installation attempts. 5. REFERENCE: Consult Microsoft Security Update Guide and relevant KB articles for patch availability and version-specific guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 25 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability exploits improper link resolution in Windows Installer (msiexec.exe and related MSI processing components), which fails to properly validate symbolic links or NTFS junctions before file access operations during package installation. CWE-59 (Link Following) describes the root cause: the application follows a link (symlink/junction) to a file without verifying the link's target is legitimate. Windows Installer processes MSI packages with SYSTEM privileges in certain contexts, creating a Time-of-Check-Time-of-Use (TOCTOU) window where an attacker can replace legitimate file paths with links pointing to sensitive system locations (e.g., %SystemRoot%, %ProgramFiles%, registry hives). The vulnerability is exacerbated because authorized users (PR:L in CVSS vector) can trigger MSI installations, and the installer's file operations are not confined by strict path validation or link-aware APIs.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
Improper link resolution before file access ('link following') in Windows Installer allows an authorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2025-33075 is a privilege escalation vulnerability in Windows Installer that allows authenticated local users to gain elevated system privileges through symlink manipulation, affecting organizations reliant on Windows-based systems and administrative processes. With a CVSS score of 7.8 and 0.5% exploitation probability, this represents a moderate near-term risk to internal security posture, particularly for environments with multiple local user accounts or shared workstations.
Apply vendor patch. Interim mitigations pending patch deployment: restrict local user account creation to authorized administrators only, implement application whitelisting to limit installer execution, and enforce multi-factor authentication for administrative privileges where feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2025-17770
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB