Authenticated arbitrary file write via unsanitized filename
Published May 7, 2026 · Updated May 7, 2026
Path traversal in Open Notebook 1.8.3 and earlier allows remote authenticated users to write arbitrary files in its Docker container. The upload endpoint uses the supplied filename as a path without sanitizing it or confirming that the resolved destination remains under the upload directory. Any application account that can upload a file can overwrite application-accessible code or configuration, interrupting service or enabling a web shell.
Summary
What happened
Path traversal in Open Notebook 1.8.3 and earlier allows remote authenticated users to write arbitrary files in its Docker container. The upload endpoint uses the supplied filename as a path without sanitizing it or confirming that the resolved destination remains under the upload directory. Any application account that can upload a file can overwrite application-accessible code or configuration, interrupting service or enabling a web shell.
The record
- CVE
- CVE-2026-33588
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Open Notebook
- Product
- Open Notebook
- Classifications
- CWE-20, CWE-22, T1105
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA filename path-traversal payloadproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo