Which versions of Open Notebook are affected by CVE-2026-33588?

Open Notebook v1.8.3 contains a path traversal vulnerability in file upload functionality that permits local attackers to write arbitrary files within the Docker container, creating risk of container…

How to fix or mitigate CVE-2026-33588?

Within 24 hours: Disable or restrict file upload functionality in Open Notebook v1.8.3 via network controls or application configuration; inventory all instances and document their network exposure. Within 7 days: Implement filesystem-level write restrictions using Docker security policies (read-only root filesystem where feasible); apply network segmentation to limit local access to affected instances. Within 30 days: Migrate to a patched version of Open Notebook when available; if unavailable, evaluate replacement solutions or implement WAF/runtime application self-protection (RASP) controls to validate upload paths.

Open Notebook CVE-2026-33588

Q: What is the CVSS score of CVE-2026-33588?

CVE-2026-33588 has a CVSS 4.0 base score of 7.0 (High). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-28347 HIGH

Improper Input Validation (CWE-20)

2026-05-07 ENISA

GHSA-c7wf-4r4p-4766

Docker File Upload Path Traversal

7.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

7.0 HIGH

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

May 07, 2026 - 11:30 vuln.today

CVSS changed

May 07, 2026 - 11:22 NVD

7.0 (HIGH)

CVE Published

May 07, 2026 - 10:28 nvd

HIGH 7.0

DescriptionCVE.org

Lack of user input validation in the file upload functionality of Open Notebook v1.8.3 allows the application user to create or modify files on the docker container via path traversal.

AnalysisAI

Path traversal in Open Notebook v1.8.3's file upload allows arbitrary file creation or modification within the Docker container filesystem. Attackers with local access can write files outside intended directories, enabling container escape scenarios, configuration tampering, or privilege escalation by overwriting critical system files. No public exploit identified at time of analysis, but the vulnerability affects default configurations where file upload is accessible.

Technical ContextAI

Open Notebook v1.8.3 suffers from CWE-20 (Improper Input Validation) in its file upload component. The application fails to sanitize user-supplied file paths, allowing directory traversal sequences (../) in upload requests. When deployed in Docker containers, this enables attackers to write beyond the intended upload directory to arbitrary locations within the container filesystem. Path traversal vulnerabilities in containerized applications are particularly dangerous as they can target Docker socket files, escape mechanisms, or volume mount points to affect the host system. The affected product is identified by CPE cpe:2.3:a:open_notebook:open_notebook:*:*:*:*:*:*:*:*, confirming the vulnerability exists across the v1.8.3 release line.

RemediationAI

Upgrade to a patched version of Open Notebook once released by the vendor - monitor https://github.com/lfnovo/open-notebook/security/advisories/GHSA-x4q2-89g5-594v for official fix announcement and version number. No vendor-released patch identified at time of analysis. Immediate compensating controls: implement strict input validation on all file upload paths using allowlist-based filename sanitization (reject any paths containing ../, absolute paths, or special characters); configure Docker container with read-only root filesystem where possible (trade-off: may break legitimate write operations to logs or temp directories); use Docker volume mounts with restricted permissions only for necessary upload directories; run container with minimal capabilities (drop CAP_DAC_OVERRIDE, CAP_CHOWN) to limit file modification scope; implement application-level access controls restricting file upload to authenticated administrators only. If file upload is not required for your use case, disable the feature entirely at the application configuration level. Each mitigation reduces attack surface but may impact functionality - test thoroughly in non-production environments first.