CVE
Guard Core denial of service in template-injection detection regex
Affects guard-core 3.5.0 through 3.12.0 with penetration detection on, which is the default, and query parameters scanned by default. No vendor rating is given beyond CVSS 7.5. Fixed in 3.13.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 3.13.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Guard Core, an API security engine, has a flaw in its built-in template-injection detection pattern. An unauthenticated attacker can send a single request over the network to freeze the shared event loop, making all application endpoints unresponsive.
Original 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.
Who should check
Teams running guard-core 3.5.0 through 3.12.0 with default configuration, including FastAPI-Guard, FlaskAPI Guard and DjAPI Guard adapters on asyncio servers
“every application embedding guard-core ≥ 3.5.0 with its default configuration”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 3.13.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129302 (Guard Core: Quadratic ReDoS in built-in detection pattern freezes the event loop with a single request), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129302 (entry last updated 2026-11-16):
Affected:
- rennf93 guard-core: from 3.5.0, fixed in 3.13.0
Fixed versions: 3.13.0.
Conditions (all must be true for the bug to be hit):
- Guard-core versions 3.5.0 through 3.12.0 (source: https://github.com/Guard-Core/guard-core/security/advisories/GHSA-r7hm-rjvg-xx7j)
- Penetration detection enabled, which is the default (source: https://github.com/Guard-Core/guard-core/security/advisories/GHSA-r7hm-rjvg-xx7j)
- Enhanced mode, which a stock SecurityConfig enables (source: https://github.com/Guard-Core/guard-core/security/advisories/GHSA-r7hm-rjvg-xx7j)
- Query parameters are scanned by default (source: https://github.com/Guard-Core/guard-core/security/advisories/GHSA-r7hm-rjvg-xx7j)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129302 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129302 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Guard-Core/guard-core/security/advisories/GHSA-r7hm-rjvg-xx7j
- https://github.com/Guard-Core/guard-core/pull/68
- https://github.com/Guard-Core/guard-core/commit/c07239fa1c5aa93e3f179440e79dad652977d3e4
- https://github.com/Guard-Core/guard-core/releases/tag/3.13.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129302
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129302"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- rennf93 guard-core
From 3.5.0 · fixed in 3.13.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129302
Is CVE-2026-129302 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A quadratic regular-expression denial-of-service flaw in a built-in detection pattern. A single unauthenticated request can freeze the event loop for seconds, which stalls every endpoint of the application, and the triggering request is not recorded as a detection.Source: github.com
Which versions are affected by CVE-2026-129302?
guard-core: from 3.5.0 before 3.13.0.Source: cve.now feed data
Am I affected, and how do I check?
Guard-core versions 3.5.0 through 3.12.0 are affected when penetration detection is enabled, which is the default, and enhanced mode is active, which a stock SecurityConfig enables. Query parameters are scanned by default. To check, look at the installed guard-core version and whether a SecurityConfig is present in the application.Source: github.com
How do I fix CVE-2026-129302?
Upgrade guard-core to 3.13.0 or later, which is the fixed version.Source: github.com