Script execution via Jupyter viewer DOM XSS
Published Feb 9, 2026 · Updated Feb 9, 2026
DOM-based XSS in the Jupyter viewer in JetBrains PyCharm before 2025.3.2 allows remote attackers to execute script in a user's IDE. JetBrains identifies the Jupyter viewer page as the affected locus but has not published which DOM source, sink, or sanitization operation mishandles attacker-controlled content. Exploitation requires a user to view crafted Jupyter content; successful script execution exposes or modifies data and can interrupt the IDE.
Summary
What happened
DOM-based XSS in the Jupyter viewer in JetBrains PyCharm before 2025.3.2 allows remote attackers to execute script in a user's IDE. JetBrains identifies the Jupyter viewer page as the affected locus but has not published which DOM source, sink, or sanitization operation mishandles attacker-controlled content. Exploitation requires a user to view crafted Jupyter content; successful script execution exposes or modifies data and can interrupt the IDE.
The record
- CVE
- CVE-2026-25847
- Published
- Feb 9, 2026
- Updated
- Feb 9, 2026
- Vendor
- JetBrains
- Product
- PyCharm
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2026CVE publishedPublication date reported by the CVE source.
- Feb 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo