CVE-2026-25847
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 · uneditedIn JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible
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 confidenceA DOM-based Cross-Site Scripting (XSS) vulnerability in the Jupyter viewer page of JetBrains PyCharm allows remote attackers to inject malicious JavaScript code that executes in the context of the user's browser session. The vulnerability stems from improper handling of user-supplied input in the DOM.
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< 2025.3.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PyCharm versionOpen PyCharm and go to Help > About (or PyCharm > About on macOS) to view the exact version number displayed in the application windowAffected if The displayed version is earlier than 2025.3.2 (for example, 2025.3.1, 2025.2.x, or older)
-
Confirm Jupyter plugin is enabledNavigate to Settings > Plugins > Installed and verify that the Jupyter plugin is installed and enabledAffected if The Jupyter plugin is enabled and installed, making the Jupyter viewer functionality available in the IDE
-
Verify Jupyter viewer is accessibleOpen any Python file in PyCharm, right-click, and check if there is an option to view in Jupyter, or check if you can open .ipynb notebook files directly in the IDEAffected if The Jupyter viewer functionality is accessible or has been used to open notebook files in PyCharm
-
Check for recent Jupyter viewer usageReview recent files or sessions where .ipynb files were opened using PyCharm's built-in Jupyter viewerAffected if You have recently used the Jupyter viewer to open or interact with notebook files in PyCharm
You are likely affected if your PyCharm version is earlier than 2025.3.2 AND you have the Jupyter plugin enabled or have used the Jupyter viewer to open notebook files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.3.2
Update JetBrains PyCharm to version 2025.3.2 or later to apply the vendor patch that addresses this vulnerability.
2025.3.2
- Open PyCharm and navigate to Help > Check for Updates (or PyCharm > Check for Updates on macOS)
- If an update to version 2025.3.2 is available, download and install it
- Alternatively, download PyCharm 2025.3.2 directly from the official JetBrains website at jetbrains.com
- Restart PyCharm after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-25847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25847 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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