GHSA-7xjm-g8f4-rp26: Giskard has Unsandboxed Jinja2 Template Rendering in ConformityCheck

Summary

giskard-checks versions before 1.0.2b1 render the ConformityCheck rule parameter through Jinja2's default Template() constructor, so template expressions in rule definitions are evaluated at runtime. If check definitions come from an untrusted source, this can lead to arbitrary code execution, though the library is a local testing tool and exploitation requires write access to a check definition followed by a developer running the test suite.

Mitigation

Upgrade to giskard-checks >= 1.0.2b1. The template rendering has been removed from rule evaluation.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• giskard-checksPyPIReaches an LLM package through dependencies · 2 tracked dependents

Related items

• MediumFake AI Attacks Spread Across US Companies: How MSSPs Can Stop Incidents EarlySimilar attack · The Hacker News
• MediumRansomware extortion gets personal as attackers target employees’ familiesSimilar attack · CSO Online
• MediumLangflow's Critical Authenticated RCE Flaw Targeted in 1,423 Honeypot Exploit AttemptsSimilar attack · The Hacker News
• MediumAnthropic 'SneakPeek' Flaw Is a Silent Zero-Click ThreatSimilar attack · Dark Reading
• HighCVE-2026-104103: Ludwig archive extraction allows writes outside extraction directorySimilar attack · NVD/CVE Database