CVE-2022-29238

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with ContentsManager.allow_hidden = False only prevented listing the contents of hidden directories, not accessing individual hidden files or files in hidden directories (i.e. hidden files were 'hidden' but not 'inaccessible'). This could lead to notebook configurations allowing authenticated access to files that may reasonably be expected to be disallowed. Because fully authenticated requests are required, this is of relatively low impact. But if a server's root directory contains sensitive files whose only protection from the server is being hidden (e.g. ~/.ssh while serving $HOME), then any authenticated requests could access files if their names are guessable. Such contexts also necessarily have full access to the server and therefore execution permissions, which also generally grants access to all the same files. So this does not generally result in any privilege escalation or increase in information access, only an additional, unintended means by which the files could be accessed. Version 6.4.12 contains a patch for this issue. There are currently no known workarounds.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 14, 2022

Last Modified

November 21, 2024

References (1)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntujupyter-notebook (5.2.2-1ubuntu0.1) @ bionic2026-05-25ubuntu

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-notebook6.2.0-1 ... 7.0.0-2 (20 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-notebook—
  • every version up to 6.4.12-1: fixed in 6.4.12-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-notebook—
  • every version up to 6.4.12-1: fixed in 6.4.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-notebook—
  • every version up to 6.4.12-1: fixed in 6.4.12-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
notebook0.0.0 ... 5.7.16 (88 versions)
  • every version up to 6.4.12: fixed in 6.4.12
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2022-29238?
CVE-2022-29238 is a medium-severity vulnerability; its CVE record was published on June 14, 2022. Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with ContentsManager.allow_hidden = False only prevented listing the contents of hidden directories, not accessing individual hidden files or files…
When was the CVE record for CVE-2022-29238 published?
The CVE record for CVE-2022-29238 was published on June 14, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-29238 actively exploited?
CVE-2022-29238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-29238?
CVE-2022-29238 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2022-29238?
A fix for CVE-2022-29238 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-29238

Explore →

Is Your Infrastructure Affected by CVE-2022-29238?

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

Book a Demo →Browse All CVEs