CVE-2026-25847: CWE-79 in JetBrains PyCharm
CVE-2026-25847 is a high-severity DOM-based Cross-Site Scripting (XSS) vulnerability affecting JetBrains PyCharm versions prior to 2025. 3. 2, specifically on the Jupyter viewer page. This vulnerability allows remote attackers to execute arbitrary scripts in the context of the affected application via crafted input that is improperly handled in the DOM. Exploitation requires user interaction but no authentication, and the vulnerability impacts confidentiality, integrity, and availability with a CVSS score of 8. 2. Although no known exploits are currently reported in the wild, the vulnerability's scope is significant due to PyCharm's widespread use among developers worldwide. Organizations using PyCharm for Jupyter notebook development or viewing should prioritize patching to mitigate potential risks. The vulnerability is particularly relevant to countries with large software development sectors and significant adoption of JetBrains products. Mitigation involves updating to PyCharm 2025.
AI Analysis
Technical Summary
CVE-2026-25847 is a DOM-based Cross-Site Scripting (XSS) vulnerability classified under CWE-79, discovered in JetBrains PyCharm before version 2025.3.2. The flaw exists on the Jupyter viewer page, where user-supplied input is improperly sanitized or escaped before being inserted into the Document Object Model (DOM). This improper handling allows attackers to inject malicious JavaScript code that executes in the context of the victim's browser session when they interact with the affected page. The vulnerability does not require authentication but does require user interaction, such as opening or viewing a maliciously crafted Jupyter notebook or URL. The CVSS v3.1 base score is 8.2, indicating a high severity level, with vector metrics AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L. This means the attack is network exploitable but requires high attack complexity and user interaction, with no privileges required. The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component, impacting confidentiality and integrity at a high level and availability at a low level. No public exploits have been reported yet, but the vulnerability poses a significant risk given PyCharm's popularity among developers for Python and Jupyter notebook development. The lack of a patch link in the provided data suggests users should monitor JetBrains advisories closely and update promptly once patches are available.
Potential Impact
The vulnerability could allow attackers to execute arbitrary scripts in the context of the PyCharm Jupyter viewer, potentially leading to theft of sensitive information such as credentials, tokens, or intellectual property contained within notebooks. It could also enable attackers to manipulate notebook content or perform actions on behalf of the user, undermining data integrity. Although availability impact is low, successful exploitation could disrupt developer workflows or lead to further compromise of development environments. Organizations relying on PyCharm for data science, machine learning, or software development may face increased risk of targeted attacks, especially in environments where notebooks are shared or accessed remotely. The high severity and scope change imply that the vulnerability could be leveraged to pivot attacks beyond the immediate application context, increasing the risk of broader compromise.
Mitigation Recommendations
The primary mitigation is to upgrade JetBrains PyCharm to version 2025.3.2 or later as soon as the patch is released. Until then, organizations should restrict access to the Jupyter viewer page, especially from untrusted networks or users. Implement strict input validation and sanitization on any user-supplied data that may be rendered in the Jupyter viewer context. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. Educate users about the risks of opening untrusted Jupyter notebooks or links within PyCharm. Monitor network traffic and application logs for suspicious activity indicative of attempted exploitation. Consider isolating development environments or using sandboxing techniques to limit the impact of potential XSS attacks. Regularly review JetBrains security advisories for updates or additional mitigations.
Affected Countries
United States, Germany, United Kingdom, France, Japan, China, India, Canada, Australia, South Korea
CVE-2026-25847: CWE-79 in JetBrains PyCharm
Description
CVE-2026-25847 is a high-severity DOM-based Cross-Site Scripting (XSS) vulnerability affecting JetBrains PyCharm versions prior to 2025. 3. 2, specifically on the Jupyter viewer page. This vulnerability allows remote attackers to execute arbitrary scripts in the context of the affected application via crafted input that is improperly handled in the DOM. Exploitation requires user interaction but no authentication, and the vulnerability impacts confidentiality, integrity, and availability with a CVSS score of 8. 2. Although no known exploits are currently reported in the wild, the vulnerability's scope is significant due to PyCharm's widespread use among developers worldwide. Organizations using PyCharm for Jupyter notebook development or viewing should prioritize patching to mitigate potential risks. The vulnerability is particularly relevant to countries with large software development sectors and significant adoption of JetBrains products. Mitigation involves updating to PyCharm 2025.
AI-Powered Analysis
Technical Analysis
CVE-2026-25847 is a DOM-based Cross-Site Scripting (XSS) vulnerability classified under CWE-79, discovered in JetBrains PyCharm before version 2025.3.2. The flaw exists on the Jupyter viewer page, where user-supplied input is improperly sanitized or escaped before being inserted into the Document Object Model (DOM). This improper handling allows attackers to inject malicious JavaScript code that executes in the context of the victim's browser session when they interact with the affected page. The vulnerability does not require authentication but does require user interaction, such as opening or viewing a maliciously crafted Jupyter notebook or URL. The CVSS v3.1 base score is 8.2, indicating a high severity level, with vector metrics AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L. This means the attack is network exploitable but requires high attack complexity and user interaction, with no privileges required. The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component, impacting confidentiality and integrity at a high level and availability at a low level. No public exploits have been reported yet, but the vulnerability poses a significant risk given PyCharm's popularity among developers for Python and Jupyter notebook development. The lack of a patch link in the provided data suggests users should monitor JetBrains advisories closely and update promptly once patches are available.
Potential Impact
The vulnerability could allow attackers to execute arbitrary scripts in the context of the PyCharm Jupyter viewer, potentially leading to theft of sensitive information such as credentials, tokens, or intellectual property contained within notebooks. It could also enable attackers to manipulate notebook content or perform actions on behalf of the user, undermining data integrity. Although availability impact is low, successful exploitation could disrupt developer workflows or lead to further compromise of development environments. Organizations relying on PyCharm for data science, machine learning, or software development may face increased risk of targeted attacks, especially in environments where notebooks are shared or accessed remotely. The high severity and scope change imply that the vulnerability could be leveraged to pivot attacks beyond the immediate application context, increasing the risk of broader compromise.
Mitigation Recommendations
The primary mitigation is to upgrade JetBrains PyCharm to version 2025.3.2 or later as soon as the patch is released. Until then, organizations should restrict access to the Jupyter viewer page, especially from untrusted networks or users. Implement strict input validation and sanitization on any user-supplied data that may be rendered in the Jupyter viewer context. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. Educate users about the risks of opening untrusted Jupyter notebooks or links within PyCharm. Monitor network traffic and application logs for suspicious activity indicative of attempted exploitation. Consider isolating development environments or using sandboxing techniques to limit the impact of potential XSS attacks. Regularly review JetBrains security advisories for updates or additional mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- JetBrains
- Date Reserved
- 2026-02-06T14:16:37.003Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6989be7b4b57a58fa145bd8d
Added to database: 2/9/2026, 11:01:15 AM
Last enriched: 2/27/2026, 8:09:20 AM
Last updated: 2/27/2026, 9:03:10 PM
Views: 207
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-28288: CWE-204: Observable Response Discrepancy in langgenius dify
MediumCVE-2026-28272: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in kiteworks security-advisories
HighCVE-2026-28271: CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action in kiteworks security-advisories
MediumCVE-2026-28270: CWE-434: Unrestricted Upload of File with Dangerous Type in kiteworks security-advisories
MediumCVE-2026-28268: CWE-459: Incomplete Cleanup in go-vikunja vikunja
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.