Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Giskard's giskard-checks package, versions before 1.0.2b1, renders the ConformityCheck rule parameter as a Jinja2 template without a sandbox, so template expressions in rule text run at evaluation time. An attacker would need to write to a check definition that a developer later runs, such as a shared project file, and could then execute arbitrary code. Upgrade to giskard-checks 1.0.2b1 or later, which removes template rendering from rule evaluation.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 4.0 | CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0015, the 4th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:59 UTC First seen by agentprime
- 31 Oct 2026, 14:59 UTC Confirmed by OSV