VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nbgrader: vulnerability history, versions and safety

nbgrader is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 1 release, from Jan 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nbgrader vulnerabilities

Vulert verdict on nbgrader 0.9.6 i

Updated on 23 Oct 2026

Good news: 0.9.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.9.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.9.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.9.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 17 packages i
  • Stars 1,374 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for nbgrader, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.9.6 30 Sep 2026 none non-standard — Details →
0.9.5 17 Jan 2025 none non-standard — Details →
0.9.4 18 Nov 2024 H1 U1 non-standard Yes Details →
0.9.3 20 Jun 2024 none non-standard — Details →
0.9.2 26 Mar 2024 none non-standard — Details →
0.9.1 05 Sep 2023 none non-standard — Details →
0.9.0 04 Sep 2023 none non-standard — Details →
0.8.5 04 Sep 2023 none non-standard — Details →
0.9.0a1 21 Jul 2023 none non-standard — Details →
0.9.0a0 18 Jul 2023 none non-standard — Details →
0.8.4 16 Jun 2023 none non-standard — Details →
0.8.3 15 Jun 2023 none non-standard — Details →
0.8.2 28 Mar 2023 none non-standard — Details →
0.8.1 27 Sep 2022 none non-standard — Details →
0.8.0 22 Aug 2022 none BSD-3-Clause — Details →
0.8.0a2 06 Jul 2022 none BSD-3-Clause — Details →
0.8.0a1 04 Jul 2022 none BSD-3-Clause — Details →
0.8.0a0 28 Jun 2022 none BSD-3-Clause — Details →
0.7.1 23 Jun 2022 none non-standard — Details →
0.7.0 07 May 2022 none non-standard — Details →
0.6.2 08 May 2021 none non-standard — Details →
0.6.1 07 Nov 2019 none non-standard — Details →
0.6.0 25 Aug 2019 none non-standard — Details →
0.5.6 21 Aug 2019 none non-standard — Details →
0.5.5 06 Jan 2019 none non-standard — Details →
0.5.4 28 Oct 2017 none non-standard — Details →
0.5.3 24 Aug 2017 none non-standard — Details →
0.5.2 20 Jul 2017 none non-standard — Details →
0.5.1 10 Jul 2017 none non-standard — Details →
0.5.0 08 Jul 2017 none non-standard — Details →
0.4.0 06 Feb 2017 none non-standard — Details →
0.4.0rc1 15 Jan 2017 none non-standard — Details →
0.3.3 13 Jan 2017 none non-standard — Details →
0.3.2 11 Jan 2017 none non-standard — Details →
0.3.1 22 Sep 2016 none non-standard — Details →
0.3.1rc0 22 Sep 2016 none non-standard — Details →
0.3.0 25 Jun 2016 none non-standard — Details →
0.2.2 03 Sep 2015 none non-standard — Details →
0.2.2.dev0 03 Sep 2015 none non-standard — Details →
0.2.1 23 Aug 2015 none non-standard — Details →
0.2.1.dev1 21 Aug 2015 none non-standard — Details →
0.2.1.dev0 21 Aug 2015 none non-standard — Details →
0.2.0 19 Aug 2015 none non-standard — Details →
0.1.0 16 Jul 2015 none non-standard — Details →

All 44 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for nbgrader

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Flaw in nbgrader: Frame-Ancestors Policy Vulnerability 8.6 high 0.9.5 17 Jan 2025
CVE-2025-23205: nbgrader Vulnerability Allows Unauthorized Access to Formgrader Content 8.6 high 0.9.5 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About nbgrader

Is nbgrader safe to use?

Vulert records 2 vulnerabilities for nbgrader in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is nbgrader's Vulert package health score?

Vulert scores nbgrader 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of nbgrader affected?

No. 0.9.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of nbgrader should I use?

0.9.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does nbgrader have?

2 vulnerabilities are recorded for nbgrader in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nbgrader vulnerabilities disclosed?

1 vulnerability was recorded for nbgrader in the last 12 months, and the oldest entry in this database dates to 17 Jan 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of nbgrader are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor nbgrader for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the nbgrader version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.