giskard-checks

Version	Released
`1.0.4` patch	Sep 14, 2026
`1.0.3` patch	Aug 26, 2026
`1.0.2` initial	Aug 26, 2026
`1.0.2rc1` pre	Aug 18, 2026
`1.0.2b6` pre	Aug 06, 2026
`1.0.2b5` pre	Jul 13, 2026
`1.0.2b4` pre	Jun 09, 2026
`1.0.2b3` pre	May 20, 2026
`1.0.2b2` pre	Apr 29, 2026
`1.0.2b1` pre	Apr 10, 2026
`1.0.1b1` pre 2 CVEs	Mar 26, 2026
`1.0.1a2` pre 2 CVEs	Mar 20, 2026
`1.0.1a1` pre 2 CVEs	Mar 12, 2026

1.0.4 patch

Sep 14, 2026

1.0.3 patch

Aug 26, 2026

1.0.2 initial

Aug 26, 2026

1.0.2rc1 pre

Aug 18, 2026

1.0.2b6 pre

Aug 06, 2026

1.0.2b5 pre

Jul 13, 2026

1.0.2b4 pre

Jun 09, 2026

1.0.2b3 pre

May 20, 2026

1.0.2b2 pre

Apr 29, 2026

1.0.2b1 pre

Apr 10, 2026

1.0.1b1 pre

2 CVEs

CVE-2026-40320 PYSEC-2026-2488 GHSA-7xjm-g8f4-rp26 Jul 13, 2026

Giskard has Unsandboxed Jinja2 Template Rendering in ConformityCheck

Critical

Local Low Low

Summary

The ConformityCheck class in giskard-checks rendered the rule parameter through Jinja2's default Template() constructor. Because the rule string is silently interpreted as a Jinja2 template, a developer may not realize that template expressions embedded in rule definitions are evaluated at runtime. In a scenario where check definitions are loaded from an untrusted source (e.g. a shared project file or externally contributed configuration), this could lead to arbitrary code execution.

giskard-checks is a local developer testing library with no network-facing service. Check definitions, including the rule parameter, are provided in application code or project configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite by a developer.

However, the implicit template evaluation of the rule parameter is not obvious from the API surface. This hidden behavior increases the likelihood of a developer inadvertently passing untrusted input to it when integrating the library into a larger system.

Affected Component

conformity.py, line 59:

from jinja2 import Template
...
formatted_rule = Template(self.rule).render(trace=trace)

Affected Versions

giskard-checks < 1.0.2b1

Patched Version

giskard-checks >= 1.0.2b1 (template parsing removed from rule evaluation entirely)

Remediation

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

Credit

Giskard-AI thanks @dhabaleshwar for identifying the unsandboxed template usage.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

CVE-2026-40319 PYSEC-2026-2489 GHSA-rq2q-4r55-9877 Jul 13, 2026

Giskard has a Regular Expression Denial of Service (ReDoS) in RegexMatching Check

Medium

Local Low Low

Summary

The RegexMatching check in the giskard-checks package passes a user-supplied regular expression pattern directly to Python's re.search() without any timeout, complexity guard, or pattern validation. An attacker who can control the regex pattern or the text being matched can craft inputs that trigger catastrophic backtracking in the regex engine, causing the process to hang indefinitely and denying service to all other operations.

giskard-checks is a local developer testing library. Check definitions, including the pattern parameter, are provided in application code or configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite. The absence of a regex timeout could cause availability issues in automated environments such as CI/CD pipelines.

Affected component

text_matching.py, line 457: re.search(pattern, text)

Remediation

Upgrade to giskard-checks >= 1.0.2b1.

Credit

Giskard-AI thanks @dhabaleshwar for identifying the missing timeout on regex evaluation.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

Mar 26, 2026

1.0.1a2 pre

2 CVEs

CVE-2026-40320 PYSEC-2026-2488 GHSA-7xjm-g8f4-rp26 Jul 13, 2026

Giskard has Unsandboxed Jinja2 Template Rendering in ConformityCheck

Critical

Local Low Low

Summary

The ConformityCheck class in giskard-checks rendered the rule parameter through Jinja2's default Template() constructor. Because the rule string is silently interpreted as a Jinja2 template, a developer may not realize that template expressions embedded in rule definitions are evaluated at runtime. In a scenario where check definitions are loaded from an untrusted source (e.g. a shared project file or externally contributed configuration), this could lead to arbitrary code execution.

giskard-checks is a local developer testing library with no network-facing service. Check definitions, including the rule parameter, are provided in application code or project configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite by a developer.

However, the implicit template evaluation of the rule parameter is not obvious from the API surface. This hidden behavior increases the likelihood of a developer inadvertently passing untrusted input to it when integrating the library into a larger system.

Affected Component

conformity.py, line 59:

from jinja2 import Template
...
formatted_rule = Template(self.rule).render(trace=trace)

Affected Versions

giskard-checks < 1.0.2b1

Patched Version

giskard-checks >= 1.0.2b1 (template parsing removed from rule evaluation entirely)

Remediation

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

Credit

Giskard-AI thanks @dhabaleshwar for identifying the unsandboxed template usage.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

CVE-2026-40319 PYSEC-2026-2489 GHSA-rq2q-4r55-9877 Jul 13, 2026

Giskard has a Regular Expression Denial of Service (ReDoS) in RegexMatching Check

Medium

Local Low Low

Summary

The RegexMatching check in the giskard-checks package passes a user-supplied regular expression pattern directly to Python's re.search() without any timeout, complexity guard, or pattern validation. An attacker who can control the regex pattern or the text being matched can craft inputs that trigger catastrophic backtracking in the regex engine, causing the process to hang indefinitely and denying service to all other operations.

giskard-checks is a local developer testing library. Check definitions, including the pattern parameter, are provided in application code or configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite. The absence of a regex timeout could cause availability issues in automated environments such as CI/CD pipelines.

Affected component

text_matching.py, line 457: re.search(pattern, text)

Remediation

Upgrade to giskard-checks >= 1.0.2b1.

Credit

Giskard-AI thanks @dhabaleshwar for identifying the missing timeout on regex evaluation.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

Mar 20, 2026

1.0.1a1 pre

2 CVEs

CVE-2026-40320 PYSEC-2026-2488 GHSA-7xjm-g8f4-rp26 Jul 13, 2026

Giskard has Unsandboxed Jinja2 Template Rendering in ConformityCheck

Critical

Local Low Low

Summary

The ConformityCheck class in giskard-checks rendered the rule parameter through Jinja2's default Template() constructor. Because the rule string is silently interpreted as a Jinja2 template, a developer may not realize that template expressions embedded in rule definitions are evaluated at runtime. In a scenario where check definitions are loaded from an untrusted source (e.g. a shared project file or externally contributed configuration), this could lead to arbitrary code execution.

giskard-checks is a local developer testing library with no network-facing service. Check definitions, including the rule parameter, are provided in application code or project configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite by a developer.

However, the implicit template evaluation of the rule parameter is not obvious from the API surface. This hidden behavior increases the likelihood of a developer inadvertently passing untrusted input to it when integrating the library into a larger system.

Affected Component

conformity.py, line 59:

from jinja2 import Template
...
formatted_rule = Template(self.rule).render(trace=trace)

Affected Versions

giskard-checks < 1.0.2b1

Patched Version

giskard-checks >= 1.0.2b1 (template parsing removed from rule evaluation entirely)

Remediation

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

Credit

Giskard-AI thanks @dhabaleshwar for identifying the unsandboxed template usage.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

CVE-2026-40319 PYSEC-2026-2489 GHSA-rq2q-4r55-9877 Jul 13, 2026

Giskard has a Regular Expression Denial of Service (ReDoS) in RegexMatching Check

Medium

Local Low Low

Summary

The RegexMatching check in the giskard-checks package passes a user-supplied regular expression pattern directly to Python's re.search() without any timeout, complexity guard, or pattern validation. An attacker who can control the regex pattern or the text being matched can craft inputs that trigger catastrophic backtracking in the regex engine, causing the process to hang indefinitely and denying service to all other operations.

giskard-checks is a local developer testing library. Check definitions, including the pattern parameter, are provided in application code or configuration files and executed locally. Exploitation requires write access to a check definition and subsequent execution of the test suite. The absence of a regex timeout could cause availability issues in automated environments such as CI/CD pipelines.

Affected component

text_matching.py, line 457: re.search(pattern, text)

Remediation

Upgrade to giskard-checks >= 1.0.2b1.

Credit

Giskard-AI thanks @dhabaleshwar for identifying the missing timeout on regex evaluation.

Affected versions


          1.0.1a1


          1.0.1a2


          1.0.1b1

Fixed in


          1.0.2b1

References

Updated Jul 13, 2026 · Source: OSV.dev

Mar 12, 2026

Activity

Details