wbond pybars3 up to 0.9.7 Compiler pybars/_compiler.py code injection

Summaryinfo

A vulnerability has been found in wbond pybars3 up to 0.9.7 and classified as critical. This affects an unknown function of the file pybars/_compiler.py of the component Compiler. The manipulation leads to code injection. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is listed as CVE-2026-119716. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in wbond pybars3 up to 0.9.7. It has been rated as critical. This issue affects an unknown part of the file pybars/_compiler.py of the component Compiler. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

pybars3 through 0.9.7 contains a code injection vulnerability in pybars/_compiler.py that allows template authors to execute Python code via unescaped bracketed path segments. Attackers can supply Handlebars templates with crafted segments in helper or block arguments to break out of string literals and execute Python in the application process.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-119716 since 10/30/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/30/2026). MITRE ATT&CK project uses the attack technique T1059 for this issue.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• wbond

Name

• pybars3

Version

• 0.9.0
• 0.9.1
• 0.9.2
• 0.9.3
• 0.9.4
• 0.9.5
• 0.9.6
• 0.9.7

Support

• end of life

Website

• Product: https://github.com/wbond/pybars3/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion