CVE-2025-64456
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 before 2025.2.4 missing signature verification in DPA Collector allows local privilege escalation
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 confidenceJetBrains ReSharper versions prior to 2025.2.4 contain a vulnerability in the DPA Collector component where signature verification is not performed, allowing a local attacker to escalate privileges on the affected system.
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.4CVSS 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.
-
Verify ReSharper is installedCheck for ReSharper installation via registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{JetBrains ReSharper} or look in Program Files for JetBrains folderAffected if ReSharper is not found on the system, the vulnerability does not apply
-
Determine installed ReSharper versionOpen ReSharper > Help > About, or check the registry value DisplayVersion under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{JetBrains ReSharper}, or inspect the version from the ReSharper DLL file in the installation directoryAffected if Unable to retrieve version information
-
Compare version against 2025.2.4Parse the version number from step 2 and compare it numerically to 2025.2.4 (e.g., 2025.2.3, 2025.1.0, 2024.x would all be vulnerable)Affected if Installed version is lower than 2025.2.4 (e.g., 2025.2.3, 2025.2.0, 2024.x)
-
Confirm DPA Collector component presenceCheck if the DPA Collector component exists in the ReSharper installation directory (look for DPA or Collector related files/dlls in the ReSharper bin folder)Affected if DPA Collector component is present and version is below 2025.2.4
The environment is affected if JetBrains ReSharper is installed with version lower than 2025.2.4 and the DPA Collector component is present on the system.
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.4
Update JetBrains ReSharper to version 2025.2.4 or later to address the missing signature verification vulnerability.
ReSharper 2025.2.4
- 1. Open JetBrains Toolbox or your IDE with ReSharper installed
- 2. Check for updates to ReSharper
- 3. If update to version 2025.2.4 is available, apply the update
- 4. Restart your IDE after the update completes
- 5. Verify the installed ReSharper version is 2025.2.4 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-64456 — 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-64456 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