Giskard Agents have Server-side template injection via ChatWorkflow.chat() using non-sandboxed Jinja2 Environment
CVE-2026-34172GHSA-frv4-x25r-588m
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (giskard-agents 1.0.2b1, 0.3.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI giskard-agents
- Affected
- <= 0.3.3>= 1.0.1a1, <= 1.0.2a1
- Fixed in
- 0.3.4, 1.0.2b1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-frv4-x25r-588m lists affected ranges: PyPI giskard-agents >=0 =1.0.1a1 <1.0.2b1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-frv4-x25r-588m lists affected ranges: PyPI giskard-agents >=0 =1.0.1a1 <=1.0.2a1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-34172: 0.64% estimated exploitation activity in the next 30 days; percentile 50.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary ChatWorkflow.chat(message) passes its string argument directly as a Jinja2 template source to a non-sandboxed Environment. A developer who passes user input to this method enables full remote code execution via Jinja2 class traversal. The method name chat and parameter name message naturally invite passing user input directly, but the string is silently parsed as a Jinja2 template, not treated as plain text. Root Cause libs/giskard-agents/src/giskard/agents/workflow.py line ~261: The string becomes contenttemplate, which is parsed by fromstring(): libs/giskard-agents/src/giskard/agents/templates/message.py lines 14-15: The Jinja2 Environment is not sandboxed: libs/giskard-agents/src/giskard/agents/templates/environment.py line 37: Proof of Concept A developer building a chatbot: Note: using .withinputs(var=userdata) is safe because variable values are not parsed as templates. The issue is only when user strings are passed directly to chat(). Impact Remote code execution on…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-frv4-x25r-588m
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-frv4-x25r-588m
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-34172 Advisory: Giskard Agents have Server-side template injection via ChatWorkflow.chat() using non-sandboxed Jinja2 Environment IDs: CVE-2026-34172, GHSA-frv4-x25r-588m Record: https://patchnext.com/advisories/cve-2026-34172 (revision 3, source checked 26 Oct 2026, 13:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: giskard-agents 1.0.2b1, 0.3.4. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI giskard-agents: affected <= 0.3.3; >= 1.0.1a1, <= 1.0.2a1; fixed in 0.3.4, 1.0.2b1 ## Suggested inspection (read-only) - `python -m pip show giskard-agents`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on giskard-agents. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-frv4-x25r-588m (OSV record GHSA-frv4-x25r-588m lists affected ranges: PyPI giskard-agents >=0 =1.0.1a1 <1.0.2b1 (fixed)) - Verified: https://github.com/advisories/GHSA-frv4-x25r-588m (GitHub-reviewed advisory GHSA-frv4-x25r-588m lists affected ranges: PyPI giskard-agents >=0 =1.0.1a1 <=1.0.2a1) Commands are suggestions: review each one before running it.
Loading voting…