CVE-2026-129303

Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injection detectors in the default detection mode

Published Nov 16, 2026 CVSS 3.1 · 3.7 Low EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

In Guard Core, the whitespace‑collapse step in the content preprocessor removes carriage returns and newlines before pattern matching. This action disables the http‑splitting and newline‑anchored command injection detectors that rely on CRLF characters, allowing malicious input containing CRLF sequences to bypass Guard Core’s built‑in protection. The weakness is a logic flaw that leads to missing detection of CRLF injection attempts (CWE‑693).

Affected Systems

The affected product is Guard Core (rennf93:guard-core), a security middleware for FastAPI‑Guard, FlaskAPI Guard, and DjAPI Guard adapters. Versions from 1.0.0 up through 3.13.0 include the vulnerable preprocessor logic. All deployments using the default enhanced detection mode during this version range are affected.

Risk and Exploitability

The CVSS score is 3.7, indicating a moderate severity. EPSS is not available and the vulnerability is not listed in CISA KEV, so there is no current evidence of exploitation in the wild. An attacker would need to supply input containing CRLF characters to a Guard Core protected endpoint; the preprocessor would strip those characters, allowing the downstream application to receive the raw CRLF sequence. If the downstream stack echoes or executes that input in a CRLF‑tolerant context such as HTTP headers or command lines, the attacker could achieve HTTP response splitting or command injection. This scenario requires that the application persist or re‑emit the value, which is a common, but not guaranteed, condition. The attack vector is therefore application‑specific and requires an additional vulnerable sink downstream.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Guard Core to version 3.13.0 or later, which restores proper handling of CRLF characters in the preprocessor.
  • If an upgrade cannot be performed immediately, modify the Guard Core source to disable the whitespace‑collapse step or use a custom preprocessor that preserves CRLF characters for vulnerable request paths.
  • Add outbound validation in the downstream application to reject or escape raw CRLF sequences before they are written to HTTP responses or executed in command contexts.

Generated by OpenCVE AI on November 16, 2026 at 20:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injection detectors in the default detection mode
Weaknesses CWE-693
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-693

    Protection Mechanism Failure

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 9:24 PM
Reserved
Nov 13, 2026, 10:30 PM
Status
Received
Published
Nov 16, 2026, 8:19 PM
Modified
Nov 16, 2026, 10:18 PM