dbcve.org
YoutrackApplication · Jetbrains

CVE-2025-64685

HIGH · 7.5 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 2025.3.104432 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In JetBrains YouTrack before 2025.3.104432 missing TLS certificate validation enabled data disclosure

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 confidence

This vulnerability in JetBrains YouTrack versions prior to 2025.3.104432 involves missing TLS certificate validation, which allows an attacker to perform man-in-the-middle (MITM) attacks and intercept sensitive data in transit. The lack of proper certificate verification means the application can be tricked into trusting malicious servers, exposing communications.

MitigationUpgrade YouTrack to version 2025.3.104432 or later which implements proper TLS certificate validation. Until upgraded, avoid using YouTrack over untrusted networks.

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
YoutrackApplication
Affected:< 2025.3.104432

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate YouTrack installation directory
    Check common installation paths: on Windows look in C:\Program Files\JetBrains\YouTrack or C:\YouTrack, on Linux/Unix check /opt/youtrack or /usr/local/youtrack, or look for the youtrack startup script/service
    Affected if YouTrack is not found in expected locations - it may not be installed or may be in a custom location
  2. Identify installed YouTrack version
    Check the version file or startup output. On Linux/Unix, run: ./youtrack.sh --version or check <install_dir>/logs for version info. On Windows, check the service properties or look for version.txt in the installation directory
    Affected if The displayed version number is lower than 2025.3.104432 (for example 2025.3.90000, 2024.x.x, etc.)
  3. Confirm version is in vulnerable range
    Compare your identified version against the affected range: any version prior to 2025.3.104432 is vulnerable. Versions 2025.3.104432 and later are patched
    Affected if Your version is < 2025.3.104432 - the application is vulnerable to MITM attacks due to missing TLS certificate validation
  4. Assess network exposure context
    Consider whether YouTrack is accessed over networks you do not fully control (public WiFi, shared networks, internet-facing deployments). The vulnerability allows attackers on the same network to intercept HTTPS traffic
    Affected if YouTrack is used over untrusted networks and the version is below 2025.3.104432 - interception of sensitive data in transit is possible

You are affected if YouTrack version is installed and the version is lower than 2025.3.104432, regardless of configuration, because the TLS certificate validation flaw exists in the application code itself.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.3.104432 or later
Fixed in 2025.3.104432
Interim mitigation

Upgrade YouTrack to version 2025.3.104432 or later which implements proper TLS certificate validation. Until upgraded, avoid using YouTrack over untrusted networks.

Recommended fix Moderate confidence

YouTrack 2025.3.104432 or later

  1. Backup your YouTrack database and configuration files before upgrading
  2. Download YouTrack version 2025.3.104432 or later from the official JetBrains website (www.jetbrains.com/youtrack)
  3. Stop the YouTrack service
  4. Install the new version following JetBrains upgrade documentation
  5. Restart the YouTrack service
  6. Verify the upgrade was successful and TLS certificate validation is now functioning properly
Caveat Review JetBrains upgrade notes for your specific upgrade path as跳跃 between major versions may require additional migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64685 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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