Vulnerability in giskard-checks (CVE-2026-40319)
Summary
Vulnerability in giskard-checks (CVE-2026-40319). Risk of unauthorized operations or information disclosure. Exploitable via text_matching.py. Mitigation: upgrade to 1.0.2b1 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40319 has been found in giskard-checks.
Attackers can target a specific entry point like text_matching.py over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade giskard-checks to 1.0.2b1 or later.
If unsure, ask your IT team or search "giskard-checks CVE-2026-40319" on the vendor's site.
CVE-2026-40319 (giskard-checks) — CWE-1333
Attack vector: local / unauthenticated
Attack surface: text_matching.py
Patched: 1.0.2b1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1333) exists in giskard-checks. Attackers reach the vulnerable code path via text_matching.py without authentication.
Check the vendor advisory for the affected versions of giskard-checks. Attack surface: text_matching.py.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.2b1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'giskard-checks' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'giskard-checks' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
giskard-checksを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade giskard-checks to 1.0.2b1ステージング環境で 1.0.2b1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com