Security readout for executives and security teams
Plain-English summary
A malicious Jupyter notebook file could run attacker-controlled code when opened in vulnerable Jupyter Notebook versions. This matters because notebooks often move between teams, vendors, students, and public repositories. The issue can turn a trusted analysis workflow into code execution on the user’s computer.
Executive priority
Treat this as urgent where Jupyter notebooks are used with external or shared content. The business risk is user workstation compromise through normal notebook workflows, not just server-side exposure.
Technical view
Jupyter Notebook relied on a deprecated Google Caja sanitizer. A public Caja bypass could trigger XSS when an untrusted .ipynb was opened, and that XSS could use Jupyter APIs to execute arbitrary code. Affected ranges are Jupyter Notebook >=6.0.0 and <6.4.1, and versions <5.7.11. CWE-79 applies.
Likely exposure
Exposure is most likely in environments where users open notebooks from external sources, shared repositories, email, courses, or research collaborations while running vulnerable Jupyter Notebook versions. Internal-only deployments are still exposed if untrusted notebooks can be introduced.
Exploitation context
The provided sources report a public Caja bypass and a malicious notebook trigger. They do not show confirmed in-the-wild exploitation, and the CVE is not marked as CISA KEV in the bundle.
Researcher notes
The evidence supports sanitizer-bypass XSS leading to arbitrary code execution via Jupyter APIs. The bundle does not provide exploit telemetry or operational indicators. Validate exposure by version and notebook trust boundaries rather than assuming internet-facing service exposure.
Mitigation direction
- Upgrade Jupyter Notebook outside the affected version ranges, such as 6.4.1 or later.
- For legacy 5.x deployments, move to 5.7.11 or later if staying on that line.
- Avoid opening untrusted .ipynb files on vulnerable Notebook installations.
- Check Jupyter’s security advisory for deployment-specific guidance.
Validation and detection
- Inventory Jupyter Notebook versions on user workstations, servers, and managed notebook images.
- Identify users or services that open notebooks from external or shared sources.
- Confirm vulnerable ranges: >=6.0.0 and <6.4.1, or <5.7.11.
- Verify patched versions are deployed before allowing untrusted notebook handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32798 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N3.95.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jupyter/notebook/security/advisories/GHSA-hwvq-6gjx-j797CVE reference · x_refsource_CONFIRM
- https://github.com/jupyter/notebook/commit/79fc76e890a8ec42f73a3d009e44ef84c14ef0d5CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.