🛡️ CVE-2025-64457 — dottrace

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

• Attack vector: Local — a local account, shell or session on the host is needed.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
• Integrity impact: Low — limited, and the attacker does not choose what is affected.
• Availability impact: None.

Weakness class

CVE-2025-64457 is classified as CWE-367: Time-of-check Time-of-use Race Condition. The state checked and the state acted upon can differ, because it may change between the two steps.

Affected software

CVE-2025-64457 is recorded against 3 packages.

• dottrace (fixed in 2025.2.5)
• resharper (fixed in 2025.2.5)
• rider (fixed in 2025.2.5)

Timeline and source

Published on 10 November 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.jetbrains.com

Other advisories for this package

dottrace has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2025-23385 (7.8 High, published 28 Jan 2025)

Same weakness in other software

These advisories are the same class of weakness (CWE-367: Time-of-check Time-of-use Race Condition) in other software:

• CVE-2022-23563 (8.0 High, published 9 Jul 2026)
• CVE-2022-23826 (published 15 May 2026)
• CVE-2022-26522 (7.8 High, published 8 May 2026)
• CVE-2022-27540 (7.8 High, published 28 Jun 2024)
• CVE-2022-23181 (8.0 High, published 6 Mar 2024)
• CVE-2022-23084 (7.5 High, published 15 Feb 2024)
• CVE-2022-24351 (4.7 Medium, published 16 Dec 2023)
• CVE-2022-31636 (7.8 High, published 13 Jun 2023)

Details

Affected Packages

References