Appsecure logo

CVE-2026-25847: High Vulnerability in JetBrains PyCharm

CVE-2026-25847 is a high-severity DOM-based XSS vulnerability in JetBrains PyCharm versions prior to 2025.3.2. Immediate patching is recommended to prevent potential exploitation.

HIGHCVSS 8.2 · Published February 9, 2026

Not a customer? See how AppSecure simulates real world attacks to protect your infrastructure.

Speak to Experts

CVE-2026-25847 is a high-severity vulnerability found in JetBrains PyCharm versions prior to 2025.3.2. This vulnerability allows for a DOM-based XSS attack on the Jupyter viewer page, posing significant security risks. Attackers may leverage this vulnerability to execute arbitrary scripts in the context of the user's browser, potentially leading to sensitive data exposure or manipulation.

The CVSS score for this vulnerability is 8.2, indicating its high severity. This score reflects the potential impact on confidentiality and integrity, which are both rated as high. Organizations using affected versions of PyCharm should prioritize patching immediately to mitigate the risk of exploitation.

As of now, no public exploits have been confirmed, and it is not included in the Known Exploited Vulnerabilities (KEV) catalog. However, given the nature of the vulnerability, organizations should remain vigilant and take necessary precautions.

Organizations should address this vulnerability in their priority patch cycle, given its potential impact and the threat landscape. The urgency of remediation is underscored by the high exploitability rating associated with this vulnerability.

Vulnerability Details

The official description states that in JetBrains PyCharm before 2025.3.2, a DOM-based XSS on the Jupyter viewer page was possible. The vulnerability is classified under CWE-79, which pertains to improper neutralization of input during web page generation.

The CVSS score of 8.2 reflects a high severity level, with an attack vector of network indicating that the vulnerability can be exploited remotely. The attack complexity is rated as high, requiring user interaction, which adds a layer of difficulty for attackers. The potential impacts include high confidentiality and integrity loss, while availability impact is rated low.

Technical Analysis

The root cause of this vulnerability lies in the failure to properly sanitize user inputs on the Jupyter viewer page. The attack vector is network-based, which means an attacker can exploit this vulnerability from a remote location. The exploit complexity is considered high, which implies that the attacker must have specific conditions to successfully exploit the vulnerability.

No privileges are required for exploitation, and user interaction is necessary, as the attack relies on the victim visiting a malicious web page. The potential impact on confidentiality and integrity is high, while availability is rated low, indicating that the service may still be operational even if the vulnerability is exploited.

Risk & Impact Analysis

Risk to organizations includes the possibility of attackers executing arbitrary scripts in the context of the user's session. This could lead to data theft, unauthorized actions, and potentially further compromise of the system. The blast radius of this vulnerability could affect any user accessing the Jupyter viewer page, making it critical for organizations to implement patches promptly.

Organizations should address this issue in their priority patch cycle due to its high severity and the potential for exploitation. The CVSS score and exploitability rating highlight the urgency of remediation efforts.

Exploitation Status

Signal

Status

Known Exploit

No

Public PoC

No

Actively Exploited

No

Ransomware Use

No

Affected Versions

The affected product is JetBrains PyCharm, with all versions prior to 2025.3.2 being vulnerable. Organizations should ensure they are using the updated version to protect against this vulnerability.

Mitigation & Remediation

Organizations should prioritize patching to the latest version of JetBrains PyCharm. If a patch is unavailable, consider implementing workarounds such as input validation and sanitization on user inputs to mitigate potential attacks. Continuous security testing should be performed to ensure the integrity of the application.

Detection Guidance

Security teams should monitor logs for unusual access patterns and validate that user inputs are properly sanitized. Behavioral anomalies in the application should also be investigated to detect potential exploitation attempts.

AppSecure Threat Intelligence Insight

The long-term significance of this vulnerability highlights the importance of secure coding practices, especially in applications with user-generated content. It reflects a trend where web applications are increasingly targeted for XSS vulnerabilities. Security teams should remain vigilant and adopt a proactive approach to identifying and remediating similar vulnerabilities in their applications.

For comprehensive testing, organizations are encouraged to engage in penetration testing to uncover similar vulnerabilities.

Further insights into secure coding can be gained through our resources on secure coding practices, which can help mitigate such vulnerabilities effectively.

Additionally, engaging in penetration testing methodology can provide organizations with the tools needed to address vulnerabilities like CVE-2026-25847.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Latest CVEs. Recently published vulnerabilities from the NVD database.

View all vulnerabilities
CVE IDSeverity
CVE-2025-65418HIGH
CVE-2025-65417MEDIUM
CVE-2025-65416MEDIUM
CVE-2025-65415MEDIUM
CVE-2025-61314HIGH

Protect Your Business with Hacker-Focused Approach.