Security Resilience

CVE-2026-33587

Lfnovo Open-Notebook ≤ 1.8.4

Published
07 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/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 Score 0.0038 30th percentile
Risk Priority 38 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-33587 is a critical-severity Improper Input Validation (CWE-20) vulnerability in Lfnovo Open-Notebook. Its CVSS base score is 9.2 (Critical).

Operationally, ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.

CWE(s)
CWE-20NVD-CWE-noinfo

Related Threats

CVEs Like This One

CVE-2026-33588Same product: Lfnovo Open-Notebook
CVE-2026-33589Same product: Lfnovo Open-Notebook
CVE-2026-28201Same product: Lfnovo Open-Notebook
CVE-2023-38720Shared CWE-20
CVE-2026-11914Shared CWE-20
CVE-2025-8414Shared CWE-20
CVE-2026-21548Shared CWE-20
CVE-2023-52552Shared CWE-20
CVE-2023-48608Shared CWE-20
CVE-2023-28911Shared CWE-20

Affected Assets

lfnovo
open-notebook
≤ 1.8.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 Information Input Validation good match

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

A.8.28 Secure coding partial match
prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.

References