# CVE-2023-51277: Security feature bypass in n/a

> Attackers can bypass macOS security restrictions in Jupyter Notebook Viewer release builds due to the get-task-allow entitlement.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-h93h-6948-g84m

## What is CVE-2023-51277?

CVE-2023-51277 is a critical vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nbviewer-app (aka Jupyter Notebook Viewer) before 0.1.6 has the get-task-allow entitlement for release builds.

## Which versions are affected by CVE-2023-51277?

It affects 1 product.


Products: Tinowagner Jupyter Notebook Viewer.

## How do I fix CVE-2023-51277?

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

## Is CVE-2023-51277 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51277 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51277 and fix it if it is affected.

What it is: CVE-2023-51277 is a critical vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51277 exists.

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-2023-51277/ (Markdown: https://insights.sbomify.com/CVE-2023-51277/index.md)
```

## Sources

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

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