CVE-2026-129303: Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injection detectors in the default detection mode
Guard Core is an API security core engine for the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters. From 1.0.0 until 3.13.0, ContentPreprocessor.preprocess() in guardcore/detectionengine/preprocessor.py collapses all whitespace before built-in pattern matching in the default enhanced mode. This removes carriage returns and newlines required by the httpsplit and newline-anchored cmdinjection detectors in guardcore/handlers/suspatternshandler.py, making those detectors unable to match. Framework-decoded CRLF can therefore pass through Guard Core unflagged while the downstream application still receives the raw newline-bearing value. Direct security impact requires a downstream stack or application that persists or re-emits the value into a CRLF-tolerant response or command context. This issue is fixed in version 3.13.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.13.0
Event History
Frequently Asked Questions
Which deployments are exposed to this detection gap?
Guard Core versions from 1.0.0 until 3.13.0 are affected when using the default enhanced detection mode. The issue applies to Guard Core used through the FastAPI-Guard, FlaskAPI Guard, or DjAPI Guard adapters.
What must be true for this to lead to a practical attack?
An attacker must supply framework-decoded CRLF-containing input that Guard Core fails to flag. A downstream stack or application must then persist or re-emit that value in a CRLF-tolerant HTTP response or command context.
Which protections are disabled by the preprocessing behavior?
The http_split detector and newline-anchored cmd_injection detectors cannot match after whitespace collapsing removes carriage returns and newlines. Other detector behavior is not described.
How can I remediate the issue?
Upgrade Guard Core to version 3.13.0, which fixes the issue. If upgrading is not immediately possible, the provided data does not specify a workaround.