# jupyter-scheduler's endpoint is missing authentication

Advisory record · `GHSA-v9g2-g7j4-4jxc`

- **Identifiers:** `GHSA-v9g2-g7j4-4jxc` · `CVE-2024-28188` · `PYSEC-2026-1479`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 23 May 2024
- **Updated:** 7 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 May 2024, 14:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `jupyter-scheduler` (PyPI): affected `>=1.0.0, <1.1.6 || >=1.2.0, <1.2.1 || >=1.3.0, <1.8.2 || >=2.0.0, <2.5.2`; fixed in `1.1.6`, `1.2.1`, `1.8.2`, `2.5.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 26th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 23 May 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-v9g2-g7j4-4jxc](https://github.com/advisories/GHSA-v9g2-g7j4-4jxc)
- [OSV: GHSA-v9g2-g7j4-4jxc](https://osv.dev/vulnerability/GHSA-v9g2-g7j4-4jxc)
- <https://github.com/jupyter-server/jupyter-scheduler/security/advisories/GHSA-v9g2-g7j4-4jxc>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-28188>
- <https://github.com/jupyter-server/jupyter_server/pull/1392>
- <https://github.com/jupyter-server/jupyter-scheduler/commit/06435a2277bb2b8f441ec9cedafa474572b92c5d>
- <https://github.com/jupyter-server/jupyter-scheduler/commit/a621b386397280cc8ee5a208dca4607cb71cdd65>
- <https://github.com/jupyter-server/jupyter-scheduler/commit/d428ac871909444e175ba421bf8ab4980d6ebf9f>
- <https://github.com/jupyter-server/jupyter-scheduler/commit/f4137a779fdf0cc4a9688a42dd8c6e7ade60f044>
- <https://github.com/jupyter-server/jupyter-scheduler>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v9g2-g7j4-4jxc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v9g2-g7j4-4jxc/>. Everything for agents: <https://agentprime.io/llms.txt>.
