CVE-2026-129302
7.5HighPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on availability
- Weakness
- CWE-400, CWE-1333
What an attacker gets
Unauthenticated attackers can trigger a denial-of-service by blocking the asyncio event loop. This causes the entire application to hang by sending a specifically crafted request that exploits inefficient regex patterns.
Root cause
The built-in template-injection detector uses an unoptimized regex pattern that causes quadratic execution time on specific inputs.
Affected versions
Guard Core 3.5.0 through 3.12.x
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Fix & remediation
Upgrade to Guard Core 3.13.0 or later. If you cannot update immediately, disable the penetration-detection feature in your SecurityConfig.
$ pip install --upgrade guard-coreAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Guard Core is an API security core engine for the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters. From 3.5.0 until 3.13.0, built-in penetration-detection patterns in guard_core/handlers/suspatterns_handler.py execute through a direct pattern.search(content) call instead of the timeout-protected create_safe_matcher() path used for custom patterns. The built-in template-injection detector contains an unbounded expression with quadratic behavior when scanning repeated opening braces. Because penetration detection and enhanced mode are enabled by a stock SecurityConfig, an unauthenticated request can block the shared asyncio event loop, affecting all application endpoints. The triggering input does not produce a detection match, so the request can complete without incrementing ban counters or being recorded as suspicious. This issue is fixed in version 3.13.0.