Skip to main content
VulnerabilityPublished Updated

CVE-2025-64456: JetBrains ReSharper · CWE-347

Affects JetBrains ReSharperSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High : upgrade to 2025.2.4 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.2.4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade JetBrains ReSharper to 2025.2.4.

Affected software

ProductAffectedFixed in
JetBrains ReSharperAffected
  • <2025.2.4
Fixed in
  • 2025.2.4

AI-suggested

1. 2. If you cannot patch yet, restrict local access to developer machines running ReSharper by enforcing strict access controls and using endpoint protection solutions to detect suspicious privilege escalation attempts. 3. Implement application whitelisting and monitor for unauthorized modifications or executions related to ReSharper components. 4. Conduct regular audits of user privileges and remove unnecessary local accounts or permissions that could be leveraged by attackers. 5. Educate developers and IT staff about the risk of local privilege escalation vulnerabilities and encourage reporting of unusual system behavior. 6. Use host-based intrusion detection systems (HIDS) to monitor for anomalous activities indicative of privilege escalation attempts. 7. Consider isolating development environments or using virtual machines to limit the impact of potential compromises. 8. Maintain comprehensive logging and monitoring to facilitate rapid detection and response to exploitation attempts.

Description

In JetBrains ReSharper before 2025.2.4 missing signature verification in DPA Collector allows local privilege escalation

References

Community reviews

Loading reviews…