Skip to main content
CVE-2026-25847VulnerabilityPublished Updated

CVE-2026-25847: JetBrains PyCharm · Cross-site Scripting

Affects JetBrains PyCharmSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High : upgrade to 2025.3.2 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.3.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Upgrade JetBrains PyCharm to 2025.3.2.

Affected software

ProductAffectedFixed in
JetBrainsPyCharmAffected
  • <2025.3.2
Fixed in
  • 2025.3.2

AI-suggested

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.

Description

In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible

References

Community reviews

Loading reviews…