# CVE-2021-42950: Code injection in n/a

> Authenticated users can execute arbitrary code by creating notebooks with malicious content, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-7ph8-5x4r-6px3

## What is CVE-2021-42950?

CVE-2021-42950 is a high-severity code injection vulnerability in n/a, published on 3 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Remote Code Execution (RCE) vulnerability exists in Zepl Notebooks all previous versions before October 25 2021. Users can register for an account and are allocated a set number of credits to try the product. Once users authenticate, they can proceed to create a new organization by which additional users can be added for various collaboration abilities, which allows malicious user to create new Zepl Notebooks with various languages, contexts, and deployment scenarios. Upon creating a new notebook with specially crafted malicious code, a user can then launch remote code execution.

## Which versions are affected by CVE-2021-42950?

It affects 1 product.


Products: Zepl Zepl.

## How do I fix CVE-2021-42950?

No fix has been published for CVE-2021-42950 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-42950 being exploited?

There is no known exploitation of CVE-2021-42950 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-42952](https://insights.sbomify.com/CVE-2021-42952/): Code injection in n/a (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42950 and fix it if it is affected.

What it is: CVE-2021-42950 is a high-severity code injection vulnerability in n/a, published on 3 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-42950 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-42950/ (Markdown: https://insights.sbomify.com/CVE-2021-42950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-42950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-42950
- OSV: https://osv.dev/vulnerability/CVE-2021-42950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-42950/
Summaries are generated and may contain mistakes; the official description above is the record.