CVE-2025-29795
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper link resolution before file access ('link following') in Microsoft Edge (Chromium-based) allows an authorized attacker to elevate privileges locally.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA link following (symlink manipulation) vulnerability in Microsoft Edge allows a local attacker with authorized access to escalate privileges by exploiting improper link resolution before file access, potentially enabling the attacker to access or modify files they shouldn't have permissions for.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.195.45CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Microsoft Edge Update componentCheck for the EdgeUpdate service or executable on the system. Common locations include C:\Program Files\Microsoft\EdgeUpdate\ or C:\Program Files (x86)\Microsoft\EdgeUpdate\. Also check Windows Services for 'Microsoft Edge Update Service'.Affected if The Edge Update component is installed on the system
-
Find the installed Edge Update version via registryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate\ or HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeUpdate\. Look for a value named 'pv' (product version) that shows the current version.Affected if The version shown is less than 1.3.195.45
-
Find the installed Edge Update version via PowerShellRun PowerShell as administrator and execute: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\EdgeUpdate' -ErrorAction SilentlyContinue | Select-Object pv. If not found under HKLM, try HKCU:\SOFTWARE\Microsoft\EdgeUpdate.Affected if The version returned is less than 1.3.195.45
-
Check Edge Update executable version directlyLocate the edgeupdate.exe file (commonly in C:\Program Files\Microsoft\EdgeUpdate\ or C:\Program Files (x86)\Microsoft\EdgeUpdate\) and right-click to view Properties, or run: (Get-Item 'C:\Program Files\Microsoft\EdgeUpdate\edgeupdate.exe').VersionInfo.FileVersionAffected if The executable version shown is less than 1.3.195.45
If the Microsoft Edge Update version is found to be lower than 1.3.195.45, the system is vulnerable to local privilege escalation via symlink manipulation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.195.45
Apply Microsoft Edge security updates when released; in the interim, restrict local access to sensitive files and directories, and limit user privileges to minimize the attack surface.
Edge Update version 1.3.195.45 or later
- Open Microsoft Edge browser
- Navigate to Settings (three-dot menu) > Help and feedback > About Microsoft Edge
- The browser will automatically check for and download updates
- Restart Edge if an update was installed
- Alternatively, ensure Windows Update is enabled and running to receive Edge Update component patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data