CVE-2026-33588
Path Traversal in Open Notebook File Upload
Publication date: 2026-05-07
Last updated on: 2026-05-07
Assigner: ENISA
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lfnovo | open_notebook | to 1.8.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-33588 is an arbitrary file write vulnerability in Open Notebook version 1.8.3 and earlier. It occurs because the file upload functionality does not properly validate user input, specifically allowing path traversal sequences in filenames.
This means an authenticated user can manipulate the filename to include directory traversal patterns (like ../../../../tmp/test.txt) to write or modify files anywhere on the docker container's filesystem.
Such manipulation can lead to overwriting application code, configuration files, or placing malicious files such as webshells in web-accessible directories.
The vulnerability is classified under CWE-22 (Path Traversal) and has been fixed in version 1.8.4 by sanitizing filenames and restricting uploads to the intended directory.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized modification or creation of files on the container hosting the application.
- Overwriting application code or configuration files, potentially leading to application malfunction or compromise.
- Placement of malicious files such as webshells in web-accessible directories, which can be used to gain further unauthorized access or control.
Because it requires low privileges and no user interaction, it poses a high risk to the integrity and availability of the application environment.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for unusual or unauthorized file writes on the docker container filesystem, especially files created or modified via the file upload functionality of Open Notebook. Look for files with path traversal sequences in their names or unexpected locations such as /tmp or web-accessible directories.
To detect exploitation attempts, you can search for files created with path traversal patterns or monitor logs for suspicious file upload requests containing sequences like "../../".
Suggested commands to detect potential exploitation include:
- On the docker container, search for recently modified files outside the expected upload directory, for example: `find / -type f -mtime -7` to find files modified in the last 7 days.
- Check for files with suspicious names containing path traversal sequences: `find / -name '*..*'` or `find / -regex '.*\.\./.*'`.
- Review web server or application logs for upload requests containing "../" sequences: `grep '\.\./' /path/to/open-notebook/logs/*`.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade Open Notebook to version 1.8.4 or later, where the file upload functionality has been patched to sanitize filenames and prevent path traversal.
Until the upgrade can be applied, restrict access to the file upload functionality to trusted users only and monitor for suspicious file uploads.
Additionally, consider implementing file system permissions to limit the locations where files can be written by the application and isolate the container environment to reduce impact.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated users to write arbitrary files on the container filesystem via path traversal, potentially leading to unauthorized modification or overwriting of application code or configuration.
Such unauthorized file manipulation can compromise data integrity and availability, which are critical aspects of compliance with standards like GDPR and HIPAA that require protection of sensitive data and system integrity.