dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2025-57728

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 2025.2 or later.
See remediation →
74/100
Remediation priority · Elevated
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 improper access control allowed Code With Me guest to discover hidden files

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, improper access control in the Code With Me collaborative editing feature allowed guest users to discover hidden files that should have been protected from disclosure.

MitigationUpgrade to IntelliJ IDEA 2025.2 or later to obtain the patch for this improper access control 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check IntelliJ IDEA version
    Open IntelliJ IDEA and go to Help > About (or on Mac: IntelliJ IDEA > About IntelliJ IDEA). Note the version number displayed.
    Affected if The version shown is earlier than 2025.2 (for example, 2025.1, 2024.x, or earlier).
  2. Verify Code With Me plugin is installed
    Go to Settings/Preferences > Plugins > Installed. Search for 'Code With Me' in the list of installed plugins.
    Affected if The Code With Me plugin is installed and enabled.
  3. Check for recent Code With Me sessions
    Look for .cwm directories in your project folders or check recent collaboration sessions in the Code With Me tool window.
    Affected if You have hosted or joined Code With Me sessions in the affected version.

You are affected if you are running any IntelliJ IDEA version prior to 2025.2 with the Code With Me plugin enabled, as guest users in your collaborative sessions could discover hidden files.

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 obtain the patch for this improper access control vulnerability.

Recommended fix High confidence

2025.2

  1. Open IntelliJ IDEA
  2. Go to Help > Check for Updates (or IntelliJ IDEA > Check for Updates on macOS)
  3. If an update to version 2025.2 or later is available, apply the update
  4. Alternatively, download IntelliJ IDEA 2025.2 or later from the official JetBrains website
  5. Restart IntelliJ IDEA after updating

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

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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