NotebookOpen Notebook up to 1.8.3 Docker Container special elements used in a template engine

Summaryinfo

A vulnerability identified as problematic has been detected in NotebookOpen Notebook up to 1.8.3. This affects an unknown part of the component Docker Container Handler. This manipulation causes improper neutralization of special elements used in a template engine. This vulnerability is registered as CVE-2026-33587. The attack needs to be launched locally. No exploit is available.

Detailsinfo

A vulnerability was found in NotebookOpen Notebook up to 1.8.3. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Docker Container Handler. The manipulation with an unknown input leads to a improper neutralization of special elements used in a template engine vulnerability. The CWE definition for the vulnerability is CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was published by CERT-EU as GHSA-f35w-wx37-26q7. The advisory is shared at github.com. This vulnerability is known as CVE-2026-33587 since 03/23/2026. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1221 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-28346). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• NotebookOpen Notebook

Version

• 1.8.0
• 1.8.1
• 1.8.2
• 1.8.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion