Back to Signal Feed
CodeTracked since May 20, 2026

Patch CVE-2026-35397 by upgrading transitive jupyter-server to 2.18.2

This pull request updates the transitive dependency jupyter-server from 2.17.0 to 2.18.2 to remediate CVE-2026-35397, and refreshes the lockfiles (uv.lock, poetry.lock, enterprise/poetry.lock) so environments resolve the fixed package version.

jupyter-serverCVE-2026-35397uv.lockpoetry.lock

What Happened

  • This pull request updates the transitive dependency jupyter-server from 2.17.0 to 2.18.2 to remediate CVE-2026-35397, and refreshes the lockfiles (uv.lock, poetry.lock, enterprise/poetry.lock) so environments resolve the fixed package version.
  • This pull request updates the transitive dependency jupyter-server from 2.17.0 to 2.18.2 to remediate CVE-2026-35397, and refreshes the lockfiles (uv.lock, poetry.lock, enterprise/poetry.lock) so environments resolve the fixed package version.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Applied a dependency-security fix by bumping the transitive jupyter-server package to the patched 2.18.2 line and synchronizing lockfiles across repository surfaces, preventing the project from continuing to build against the vulnerable 2.17.0-era runtime.

Why Track This

Why It Matters

Operators and teams deploying OpenHands get lower practical security risk because instances that consume these updated lockfiles are no longer tied to the vulnerable jupyter-server revision, reducing exposure to CVE-2026-35397. Technically, the PR aligns dependency resolution to jupyter-server 2.18.2 across uv and poetry lock files without changing project manifests. Continue monitoring whether all build/packaging paths actually use the updated lock state and whether any downstream runtime paths still resolve 2.17.x due to cached or external dependency overrides.

Impact

Operators and teams deploying OpenHands get lower practical security risk because instances that consume these updated lockfiles are no longer tied to the vulnerable jupyter-server revision, reducing exposure to CVE-2026-35397. Technically, the PR aligns dependency resolution to jupyter-server 2.18.2 across uv and poetry lock files without changing project manifests. Continue monitoring whether all build/packaging paths actually use the updated lock state and whether any downstream runtime paths still resolve 2.17.x due to cached or external dependency overrides.

What To Watch Next

  • Watch whether jupyter-server becomes a repeated pattern.
  • Track follow-up changes around AI Security.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: lockfile_drift_across_environments, deployment_images_using_stale_jupyter_server.
Open Topic TimelineOpen Technical EventOpen Original Sourcelockfile_drift_across_environments / deployment_images_using_stale_jupyter_server / insufficient_dependency_security_test_coverage / transitive_override_bypassing_lockfile

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

all-hands-ai/openhands PR #14435: Fix CVE-2026-35397: Update jupyter-server to 2.18.2

Security fix request explicitly states: jupyter-server was upgraded from 2.17.0 to 2.18.2 to address CVE-2026-35397, with lockfiles updated via uv/poetry commands and no manifest file changes.