CVE-2026-33589
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLack of user input validation in the file upload functionality of Open Notebook v1.8.3 allows the application user to access local files content from the docker container via path traversal.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe file upload functionality in Open Notebook v1.8.3 lacks proper user input validation, allowing attackers to use path traversal sequences (such as ../) in upload paths to escape the intended directory and read arbitrary local files from the docker container.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.8.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Open Notebook versionCheck the installed version of Open Notebook by examining the application banner, package metadata, or running 'open-notebook --version' if CLI is availableAffected if The installed version is lower than 1.8.4 (e.g., 1.8.3 or earlier)
-
Locate file upload functionalityExamine the application's web interface or API endpoints for file upload capability; check routes/handlers for upload-related paths (e.g., /upload, /file/upload)Affected if File upload endpoint exists and accepts path parameters for specifying upload destination
-
Verify upload path configurationReview application configuration files for upload directory settings; check if path parameters are used without sanitization in upload handlersAffected if Upload functionality accepts user-supplied path parameters without validation or path normalization checks
-
Inspect for traversal vulnerabilityTest file upload with path parameter containing ../ sequences to confirm if directory traversal is possible (in a test environment only)Affected if The application allows escaping the intended upload directory via path traversal sequences in the upload path parameter
The environment is affected if Open Notebook version is below 1.8.4 AND the file upload feature is enabled with user-controllable path parameters that are not validated for path traversal sequences.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.8.4
Implement strict input validation and path sanitization on file upload paths, using path normalization and allowlisting to prevent traversal sequences; store uploads in isolated, non-privileged directories with restricted file permissions.
Open Notebook 1.8.4
- 1. Identify the current version of Open Notebook running in your environment
- 2. If running a version lower than 1.8.4, plan for an upgrade to version 1.8.4 or later
- 3. Obtain the updated Open Notebook version 1.8.4 from the official GitHub repository
- 4. Backup your current Open Notebook configuration and data
- 5. Stop the current Open Notebook service
- 6. Deploy version 1.8.4 of Open Notebook
- 7. Verify the upgrade was successful and the application is functional
- 8. Test that the file upload functionality now properly validates input and prevents path traversal
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data