Authenticated code execution via crafted notebooks
Published Mar 3, 2022 · Updated Jul 9, 2026
Remote code execution in Zepl Notebooks before 2021-10-25 allows remote authenticated users to execute code through a crafted notebook. The disclosure identifies notebook creation and execution as the locus but does not describe the missing validation or isolation control that makes crafted code unsafe. An account with permission to create an organization and notebook is required, and successful exploitation executes code in the hosted notebook context.
Summary
What happened
Remote code execution in Zepl Notebooks before 2021-10-25 allows remote authenticated users to execute code through a crafted notebook. The disclosure identifies notebook creation and execution as the locus but does not describe the missing validation or isolation control that makes crafted code unsafe. An account with permission to create an organization and notebook is required, and successful exploitation executes code in the hosted notebook context.
The record
- CVE
- CVE-2021-42950
- Published
- Mar 3, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2022CVE publishedPublication date reported by the CVE source.
- Jul 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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