CVE-2026-129302: Guard Core: Quadratic ReDoS in built-in detection pattern freezes the event loop with a single request

Published Nov 16, 2026
·
Updated

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 guardcore/handlers/suspatternshandler.py execute through a direct pattern.search(content) call instead of the timeout-protected createsafematcher() 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.

Affected Software

1 affected component
pypi/guard-core>=3.5.0<3.13.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.13.0

Event History

Nov 16, 2026
CVE Published
via MITRE·07:36 PM
Data Sourced
via MITRE·07:36 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed by default?

Applications using Guard Core from 3.5.0 up to, but not including, 3.13.0 are affected when the built-in penetration-detection patterns are used. Stock SecurityConfig enables penetration detection and enhanced mode, so a default configuration is exposed.

2

What does an attacker need to do to trigger the issue?

No authentication, privileges, or user interaction are required. A single request containing repeated opening braces can cause quadratic processing in the built-in template-injection detector and block the shared asyncio event loop.

3

Will attempted exploitation be visible in Guard Core detection or ban records?

Not necessarily. The triggering input does not produce a detection match, so the request can complete without being recorded as suspicious or incrementing ban counters.

4

What version resolves the issue?

Upgrade Guard Core to version 3.13.0, which fixes the unsafe direct pattern search used by the built-in patterns.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203