dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2025-57727

HIGH · 7.5 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 2025.2 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 IntelliJ IDEA before 2025.2 credentials disclosure was possible via remote reference

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

In JetBrains IntelliJ IDEA versions prior to 2025.2, a vulnerability allowed credential disclosure through a remote reference mechanism. This could expose sensitive authentication credentials stored or referenced within the IDE when connecting to remote resources.

MitigationUpgrade to IntelliJ IDEA 2025.2 or later to remediate the credential disclosure vulnerability.

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
Intellij IdeaApplication
Affected:< 2025.2

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. Identify installed IntelliJ IDEA version
    Open IntelliJ IDEA, go to Help > About (on Windows/Linux) or IntelliJ IDEA > About (on macOS). The version number is displayed in the dialog. Alternatively, check the installation directory or use the command: idea --version
    Affected if The version displayed is earlier than 2025.2 (for example, 2025.1, 2024.x, or earlier)
  2. Review remote run configurations
    Inspect any run/debug configurations that connect to remote servers. Go to Run > Edit Configurations and look for configurations with remote deployment, remote interpreters, or SSH tunnel options enabled
    Affected if Remote run configurations exist that store or reference authentication credentials for connecting to remote systems
  3. Examine SSH and remote connection settings
    Navigate to Settings > Build, Execution, Deployment > SSH configurations, or Settings > Tools > SSH Terminal. Check for saved SSH credentials or key-based authentication configurations
    Affected if SSH connection profiles exist that contain stored username/password combinations or reference credential files for remote access
  4. Check database and data source connections
    Go to View > Tool Windows > Database, or Settings > Data Sources. Inspect any database connections that use authentication credentials stored within the IDE
    Affected if Database data sources are configured with stored credentials for connecting to remote database servers

A user is affected if their installed IntelliJ IDEA version is earlier than 2025.2 AND they have remote connection configurations (run configurations, SSH connections, or data sources) that store or reference authentication credentials within the IDE.

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.2 or later
Fixed in 2025.2
Interim mitigation

Upgrade to IntelliJ IDEA 2025.2 or later to remediate the credential disclosure vulnerability.

Recommended fix High confidence

IntelliJ IDEA 2025.2

  1. 1. Back up your current IntelliJ IDEA configuration and projects
  2. 2. Open IntelliJ IDEA and navigate to Help > Check for Updates
  3. 3. Download and install version 2025.2 or later from the official JetBrains website (www.jetbrains.com/idea/download)
  4. 4. After installation, restart IntelliJ IDEA
  5. 5. Verify the version by checking Help > About to confirm version 2025.2 or higher is installed

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

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57727 — 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-57727 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