CVE-2026-73627

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

JupyterLab (pip package 'jupyterlab') versions >=4.1.0,<=4.5.9 and >=4.6.0,<=4.6.1 contain a plugin manager lock-rule enforcement bypass. Two server-side enforcement gaps allow an authenticated user to circumvent administrator lock rules by making direct requests to the /lab/api/plugins endpoint, enabling or disabling plugins that were locked — including child plugins of multi-plugin extensions and plugins locked via the 'lock all' mechanism. This can impact data integrity and bypass hardening or restrictions (e.g., download/upload limits) implemented through locked plugins. Fixed in versions 4.6.2 and 4.5.10.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available. Sources: github.
generic Patch Available

JupyterLab 4.6.0 Plugin Manager Lock-Rule Enforcement Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/jupyterlab-plugin-manager-lock-rule-enforcement-bypass
github Patch Available

JupyterLab PluginManager lock-rule enforcement bypass · Advisory · jupyterlab/jupyterlab · GitHub

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-h5v5-8746-g7mm

Vendor Advisories for CVE-2026-73627(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (29 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (26 versions)
  • every version up to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4: fixed in 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.1.0 ... 4.5.9 (82 versions)
  • 4.6.0 up to 4.6.2: fixed in 4.6.2
  • 4.1.0 up to 4.5.10: fixed in 4.5.10
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 100× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 173 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:24 UTCVendor advisory
  3. 2026-10-04 22:24 UTCGHSA enrichment
  4. 2026-10-03 19:53 UTCEG score recompute
  5. 2026-10-03 19:53 UTCVendor advisory
  6. 2026-10-03 19:53 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 08:05 UTCEG score recompute
  9. 2026-10-02 08:05 UTCVendor advisory
  10. 2026-10-02 08:05 UTCGHSA enrichment
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 18:43 UTCEG score recompute
  13. 2026-09-30 18:43 UTCVendor advisory
  14. 2026-09-30 18:43 UTCGHSA enrichment
  15. 2026-09-30 17:39 UTCEG score recompute
  16. 2026-09-30 17:39 UTCVendor advisory
  17. 2026-09-30 17:39 UTCGHSA enrichment
  18. 2026-09-29 15:24 UTCEPSS rescore
  19. 2026-09-29 07:19 UTCEG score recompute
  20. 2026-09-29 07:19 UTCVendor advisory
  21. 2026-09-29 07:19 UTCGHSA enrichment
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-28 08:32 UTCEG score recompute
  24. 2026-09-28 08:32 UTCVendor advisory
  25. 2026-09-28 08:32 UTCGHSA enrichment
Show 75 more
  1. 2026-09-27 13:48 UTCEPSS rescore
  2. 2026-09-27 09:48 UTCEG score recompute
  3. 2026-09-27 09:48 UTCVendor advisory
  4. 2026-09-27 09:48 UTCGHSA enrichment
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-25 04:35 UTCEG score recompute
  7. 2026-09-25 04:35 UTCVendor advisory
  8. 2026-09-25 04:35 UTCGHSA enrichment
  9. 2026-09-24 05:50 UTCEG score recompute
  10. 2026-09-24 05:50 UTCVendor advisory
  11. 2026-09-24 05:50 UTCGHSA enrichment
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-23 07:06 UTCEG score recompute
  14. 2026-09-23 07:06 UTCVendor advisory
  15. 2026-09-23 07:06 UTCGHSA enrichment
  16. 2026-09-22 08:22 UTCEG score recompute
  17. 2026-09-22 08:22 UTCVendor advisory
  18. 2026-09-22 08:22 UTCGHSA enrichment
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-21 09:37 UTCEG score recompute
  21. 2026-09-21 09:37 UTCVendor advisory
  22. 2026-09-21 09:37 UTCGHSA enrichment
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-20 10:10 UTCEG score recompute
  25. 2026-09-20 10:10 UTCVendor advisory
  26. 2026-09-20 10:10 UTCGHSA enrichment
  27. 2026-09-19 11:16 UTCEG score recompute
  28. 2026-09-19 11:16 UTCVendor advisory
  29. 2026-09-19 11:16 UTCGHSA enrichment
  30. 2026-09-18 19:28 UTCEPSS rescore
  31. 2026-09-18 10:53 UTCEG score recompute
  32. 2026-09-18 10:53 UTCVendor advisory
  33. 2026-09-18 10:53 UTCGHSA enrichment
  34. 2026-09-17 12:09 UTCEG score recompute
  35. 2026-09-17 12:09 UTCVendor advisory
  36. 2026-09-17 12:09 UTCGHSA enrichment
  37. 2026-09-16 14:08 UTCEPSS rescore
  38. 2026-09-16 12:07 UTCEG score recompute
  39. 2026-09-16 12:07 UTCVendor advisory
  40. 2026-09-16 12:07 UTCGHSA enrichment
  41. 2026-09-16 05:15 UTCEPSS rescore
  42. 2026-09-15 13:22 UTCEG score recompute
  43. 2026-09-15 13:22 UTCVendor advisory
  44. 2026-09-15 13:22 UTCGHSA enrichment
  45. 2026-09-15 03:12 UTCEPSS rescore
  46. 2026-09-14 14:38 UTCEG score recompute
  47. 2026-09-14 14:38 UTCVendor advisory
  48. 2026-09-14 14:38 UTCGHSA enrichment
  49. 2026-09-13 15:50 UTCVendor advisory
  50. 2026-09-13 15:50 UTCGHSA enrichment
  51. 2026-09-12 17:06 UTCEG score recompute
  52. 2026-09-12 17:06 UTCVendor advisory
  53. 2026-09-12 17:06 UTCGHSA enrichment
  54. 2026-09-12 15:02 UTCEPSS rescore
  55. 2026-09-11 18:21 UTCEG score recompute
  56. 2026-09-11 18:21 UTCVendor advisory
  57. 2026-09-11 18:21 UTCGHSA enrichment
  58. 2026-09-11 14:53 UTCEPSS rescore
  59. 2026-09-10 19:36 UTCEG score recompute
  60. 2026-09-10 19:36 UTCVendor advisory
  61. 2026-09-10 19:36 UTCGHSA enrichment
  62. 2026-09-10 09:35 UTCEPSS rescore
  63. 2026-09-09 20:51 UTCVendor advisory
  64. 2026-09-09 20:51 UTCGHSA enrichment
  65. 2026-09-09 05:06 UTCEG score recompute
  66. 2026-09-09 05:06 UTCVendor advisory
  67. 2026-09-09 05:06 UTCGHSA enrichment
  68. 2026-09-08 22:01 UTCEPSS rescore
  69. 2026-09-07 22:15 UTCEG score recompute
  70. 2026-09-07 22:15 UTCGHSA enrichment
  71. 2026-09-06 23:28 UTCEG score recompute
  72. 2026-09-06 23:28 UTCGHSA enrichment
  73. 2026-09-06 13:48 UTCEPSS rescore
  74. 2026-09-06 00:44 UTCEG score recompute
  75. 2026-09-06 00:44 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73627?
CVE-2026-73627 is a medium vulnerability published on August 13, 2026. JupyterLab (pip package 'jupyterlab') versions >=4.1.0,<=4.5.9 and >=4.6.0,<=4.6.1 contain a plugin manager lock-rule enforcement bypass. Two server-side enforcement gaps allow an authenticated user to circumvent administrator lock rules by making direct requests to the /lab/api/plugins endpoint,…
When was CVE-2026-73627 disclosed?
CVE-2026-73627 was first published on August 13, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73627 actively exploited?
CVE-2026-73627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73627?
CVE-2026-73627 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73627?
A fix for CVE-2026-73627 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73627 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73627

Explore →

Is Your Infrastructure Affected by CVE-2026-73627?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs