CVE-2026-129303 · Package
NO FIX YET · SEE WHAT TO DO
Guard Core, the security engine behind the FastAPI, Flask and Django Guard adapters, collapses newlines before its built-in detection rules run, so header-splitting and newline-based command injection patterns stop matching. An attacker can send CRLF-bearing input that passes unflagged and reaches the application with the newline intact, which matters only if the application then writes that value into a response or command.
first public Aug 25, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that use Guard Core through the FastAPI, Flask or Django adapters on versions from 1.0.0 up to 3.13.0. Exposure also needs a downstream part of the application that stores the request value and echoes it into a CRLF-tolerant response or command, which the sources describe as the condition for direct impact. Teams that do not use these adapters, or that run a newer version, can skip it.
Not affected if no-downstream-echo, version-3.13.0-or-later
Who cares djapi-guard, fastapi-guard, flaskapi-guard, guard-core, python
guard-core version in your Python environment, for example with pip show guard-core.fastapi-guard, flaskapi-guard or djapi-guard in your dependencies and confirm which guard-core version they pull in.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 guard_core/detection_engine/preprocessor.py collapses all whitespace before built-in pattern matching in the default enhanced mode. This removes carriage returns and newlines required by the http_split and newline-anchored cmd_injection detectors in guard_core/handlers/suspatterns_handler.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
guard-core 3.13.0 (fixed version per the sources).NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.