CVE-2025-64457
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 · uneditedIn JetBrains ReSharper, Rider and dotTrace before 2025.2.5 local privilege escalation was possible via race condition
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 race condition in JetBrains ReSharper, Rider, and dotTrace versions prior to 2025.2.5 allows a local attacker to escalate privileges. The vulnerability stems from improper synchronization in file or resource handling that can be exploited by winning a race to gain elevated access.
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< 2025.2.5< 2025.2.5< 2025.2.5CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Identify installed JetBrains productsCheck for JetBrains Rider, ReSharper, or dotTrace installations in Program Files, or use JetBrains Toolbox to list installed tools. For ReSharper, open Visual Studio and check Extensions > Manage Extensions.Affected if Any of these three products are installed on the system
-
Determine Rider versionOpen Rider IDE and navigate to Help > About (or press Ctrl+Alt+/). Alternatively, check the Rider installation directory for version information in the application files.Affected if Rider version is present and less than 2025.2.5
-
Determine ReSharper versionOpen Visual Studio with ReSharper installed, go to ReSharper > Help > About ReSharper. The version number will be displayed in the dialog.Affected if ReSharper version is present and less than 2025.2.5
-
Determine dotTrace versionOpen the dotTrace standalone application or access it via Rider's profiler (Profile > dotTrace). Check the About section for the version number.Affected if dotTrace version is present and less than 2025.2.5
The user is affected if any installed JetBrains Rider, ReSharper, or dotTrace version is found to be lower than 2025.2.5.
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 · scoped2025.2.5
Update JetBrains ReSharper, Rider, and dotTrace to version 2025.2.5 or later to remediate the privilege escalation vulnerability.
2025.2.5 or later for DotTrace, ReSharper, and Rider
- 1. Close all JetBrains IDE instances (ReSharper, Rider) and dotTrace applications
- 2. Ensure all running processes related to the affected software are terminated
- 3. Download the fixed version (2025.2.5) or later from the official JetBrains website at www.jetbrains.com
- 4. Run the installer and follow the on-screen instructions to update the software
- 5. After installation, restart your IDE or development environment
- 6. Verify the installed version matches 2025.2.5 or later to confirm the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64457 — 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-64457 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