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


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-xvx4-89q3-mchg, openSUSE-SU-2026:12503-1

## What is CVE-2026-119716?

CVE-2026-119716 is a critical vulnerability in up9inc pybars3, published on 30 Oct 2026. 

### Official description

pybars3 through 0.9.7 and pybars4 through 0.9.13 contain 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-119716?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-pybars3` | openSUSE:Tumbleweed | All versions | 0.9.7-3.1 |

## How do I fix CVE-2026-119716?

Upgrade to a fixed version.

## Is CVE-2026-119716 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119716 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119716 and fix it if it is affected.

What it is: CVE-2026-119716 is a critical vulnerability in up9inc pybars3, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119716 exists.

Affected product: up9inc pybars3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119716/ (Markdown: https://insights.sbomify.com/CVE-2026-119716/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119716
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119716
- OSV: https://osv.dev/vulnerability/CVE-2026-119716

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119716/
Summaries are generated and may contain mistakes; the official description above is the record.