CVE-2025-55247
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 .NET 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 confidenceThis is a link following (symlink) vulnerability in .NET where the application fails to properly resolve symbolic links before accessing files. An authorized attacker can exploit this to perform local privilege escalation by manipulating file system links to access protected resources or execute code with elevated privileges.
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>= 8.0.0, < 8.0.21>= 9.0.0, < 9.0.10CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Check installed .NET 8 runtime versionRun `dotnet --list-runtimes` or check the registry at `HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedfx\Microsoft.WindowsDesktop.App` for .NET Desktop RuntimeAffected if The version listed is >= 8.0.0 and < 8.0.21
-
Check installed .NET 9 runtime versionRun `dotnet --list-runtimes` or check the registry at `HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedfx\Microsoft.WindowsDesktop.App` for .NET Desktop RuntimeAffected if The version listed is >= 9.0.0 and < 9.0.10
-
Check installed .NET SDK versionRun `dotnet --list-sdks` to see installed SDK versionsAffected if The SDK version is in an affected range and you use the SDK to build or run applications locally
You are affected if any installed .NET runtime or SDK version falls within 8.0.0 through 8.0.20 or 9.0.0 through 9.0.9, as these versions contain the symlink resolution flaw.
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 · scoped8.0.219.0.10
Apply Microsoft .NET security patches as they become available. Review file system access patterns in .NET applications and implement proper link resolution validation before file operations.
Upgrade to .NET 8.0.21 or later for 8.x deployments; upgrade to .NET 9.0.10 or later for 9.x deployments
- Identify the current .NET version by running 'dotnet --version' in the terminal
- Determine whether the application uses .NET 8.x or .NET 9.x based on the project file or installed runtime
- For .NET 8.x deployments: Update the SDK and runtime to version 8.0.21 or later using the official installer or package manager
- For .NET 9.x deployments: Update the SDK and runtime to version 9.0.10 or later using the official installer or package manager
- After upgrading, verify the new version is active by running 'dotnet --version'
- Rebuild and redeploy the application to ensure compatibility with the updated runtime
- Test the application thoroughly to confirm functionality is preserved after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55247 — 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-55247 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