VulnerabilityPublished 20 Aug 2025

CVE-2025-57727: JetBrains IntelliJ IDEA · Cleartext Transmission

Affects JetBrains IntelliJ IDEASource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium · fixed in 2025.2 : update JetBrains IntelliJ IDEA when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JetBrains IntelliJ IDEA	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately plan to upgrade all IntelliJ IDEA installations to version 2025.2 or later once the patch is officially released by JetBrains. 2) Until a patch is available, restrict network access to IntelliJ IDEA instances, especially from untrusted networks, to reduce exposure to remote exploitation. 3) Educate developers and users about the risk of social engineering attacks that could trigger the required user interaction for exploitation. 4) Implement network-level monitoring and anomaly detection to identify unusual access patterns or credential usage originating from IntelliJ IDEA environments. 5) Enforce strong credential management practices, including the use of multi-factor authentication (MFA) on services accessed via IntelliJ IDEA, to limit the impact of credential disclosure. 6) Review and audit any remote references or integrations within IntelliJ IDEA configurations to minimize unnecessary exposure. 7) Maintain an incident response plan that includes steps for credential compromise scenarios, including immediate credential rotation and access revocation.

Description

In JetBrains IntelliJ IDEA before 2025.2 credentials disclosure was possible via remote reference

Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality of credentials used within IntelliJ IDEA environments. Since IntelliJ IDEA is extensively used by developers across Europe for building and maintaining software, exposure of credentials could lead to unauthorized access to development resources, source code repositories, or connected services. This could facilitate further attacks such as intellectual property theft, insertion of malicious code, or unauthorized access to internal systems. The requirement for user interaction means that social engineering or phishing tactics could be employed to trigger the vulnerability. The scope change indicates that the vulnerability could affect multiple components or systems beyond the IDE itself, potentially amplifying the impact. While the vulnerability does not directly affect system integrity or availability, the compromise of credentials can have cascading effects on organizational security posture. European organizations with stringent data protection regulations (e.g., GDPR) must consider the implications of credential exposure and potential data breaches resulting from exploitation.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Aug 2025, 09:35 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats