CVE-2026-33588
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 create or modify files on 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 confidenceOpen Notebook v1.8.3 contains a path traversal vulnerability in its file upload functionality due to insufficient user input validation. An authenticated user can craft file upload requests containing '../' sequences to escape the intended upload directory and write files to arbitrary locations on the underlying docker container filesystem, potentially overwriting configuration files or placing malicious content outside the designated upload path.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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 installed Open Notebook versionCheck the application's version information through its web interface, API endpoint, or check the Docker container label/environment variables. Compare against the affected range: versions prior to 1.8.4 are vulnerable.Affected if The installed version is Lfnovo Open Notebook and is earlier than 1.8.4
-
Verify file upload functionality is enabledInspect the application configuration files or settings to determine if the file upload feature is currently active. Look for upload-related configuration flags or module settings.Affected if File upload functionality is enabled in the application configuration
-
Confirm authentication is configuredReview the application's authentication settings to verify that user authentication is required for access. Check if anonymous or unauthenticated access is permitted.Affected if User authentication is required for application access (this is actually a prerequisite - the vulnerability requires an authenticated user)
-
Inspect upload directory configurationExamine the application configuration to identify the designated upload directory path. Check if path validation or directory restrictions are defined for uploaded files.Affected if The upload directory is not restricted through whitelisting or path validation controls
A user is affected if they are running Lfnovo Open Notebook version earlier than 1.8.4 with file upload functionality enabled and authentication configured, as the path traversal can only be exploited by authenticated users accessing the upload feature.
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 on the file upload functionality by sanitizing filename inputs, using basename() to extract only the filename, enforcing whitelisted allowed directories, and rejecting any paths containing directory traversal sequences ('../' or '..\').
v1.8.4
- 1. Backup your existing Open Notebook installation and any important data
- 2. Download the fixed version (v1.8.4) from the official GitHub repository
- 3. Replace the existing installation with the new version, preserving configuration files if needed
- 4. Verify that file upload functionality works correctly in the new version
- 5. Test that path traversal attempts are now properly sanitized/rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33588 — 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-33588 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