CVE-2025-47181
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 · high confidenceA link following (symlink manipulation) vulnerability in Microsoft Edge Chromium allows a local authenticated attacker to escalate privileges by tricking the browser into following malicious symbolic links to access sensitive files or directories they wouldn't normally have access to.
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.61CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 component versionOpen Control Panel > Programs and Features, look for 'Microsoft Edge Update' in the installed programs list, and note the version number shownAffected if The installed version of Microsoft Edge Update is lower than 1.3.195.61
-
Alternative: Check Edge Update via registryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate\ClientInstall (or similar Edge Update key), then locate the version valueAffected if The version value found in the registry is less than 1.3.195.61
-
Check if Microsoft Edge Update service existsOpen Services (services.msc) and look for a service related to Edge Update, or check Task Manager for running EdgeUpdate processesAffected if The Edge Update service or process is present and its version cannot be determined or is below 1.3.195.61
-
Verify Edge browser version as secondary indicatorLaunch Microsoft Edge, go to edge://settings/help, and note the browser version displayedAffected if The Edge browser version corresponds to an update package older than 1.3.195.61, which typically indicates the Edge Update component is also outdated
You are affected if the Microsoft Edge Update component version is installed and is less than 1.3.195.61, as this is the specific vulnerable component in this CVE.
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.61
Apply the latest Microsoft Edge security update to address the improper link resolution vulnerability.
Microsoft Edge (Chromium) with Edge Update component version 1.3.195.61 or later
- Open Microsoft Edge and navigate to Settings > About Microsoft Edge to check the current version
- Ensure Edge automatic updates are enabled: go to Settings > Privacy, search, and services > Service side component > Enable 'Keep Microsoft Edge up to date'
- Launch Edge and let it automatically update, or manually trigger an update via the update button in the About page
- Restart Edge completely after the update completes
- Revert to Settings > About Microsoft Edge and confirm the version is 1.3.195.61 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47181 — 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-47181 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