<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T04:57:19.851915+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-129303</id>
    <title>fkie_cve-2026-129303</title>
    <updated>2026-11-21T04:57:19.853728+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-129303"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-w7wg-6q7v-44f2</id>
    <title>GHSA-w7wg-6q7v-44f2 — Guard Core: Whitespace-collapse preprocessing permanently disables the CRLF-anchored http-splitting and command-injecti…</title>
    <updated>2026-11-21T04:57:19.853810+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: guard-core</p>
<p>### Summary</p>
<p>In the default "enhanced" detection mode, `ContentPreprocessor.preprocess()` collapses all whitespace (`re.sub(r"\s+", " ", content)`, `guard_core/detection_engine/preprocessor.py:137` on master `08780f1`; `:384` in the 3.12.0 sdist) **before** pattern matching. This erases every `\r` and `\n` from the scanned value, rendering two built-in detectors structurally unmatchable regardless of input:</p>
<p>- http_split — `guard_core/handlers/suspatterns_handler.py:540`: `r"[\r\n]\s*(?:HTTP\/[0-9.]+|Location:|Set-Cookie:)"` requires a literal `\r` or `\n`, which no longer exists after preprocessing;
- cmd_injection — `r"\n\s*(?:bash|sh|...)\s+-c\b"` — same structural death.</p>
<p>The downstream application receives the **raw** value with CRLF intact (Starlette percent-decodes `%0d%0a` in query parameters before the adapter passes `request.query_params.items()` to `guard_core/utils.py:843-865`), so a response-splitting-shaped payload passes detection unflagged.</p>
<p>### Details</p>
<p>Verified end-to-end against a real uvicorn server running the fastapi-guard adapter over guard-core 3.12.0, default config:</p>
<p>| request (`?q=`) | status |
|---|---|
| `value%0d%0aHTTP%2F1.1+200+OK%0d%0aSet-Cookie%3A+pwned%3D1` (decoded to literal CRLF by the framework) | **200 — missed** |
| `' OR 1=1--` | 400 — blocked (detection otherwise working) |
| `1 UNION SELECT password FROM users--` | 400 — blocked |
| `; cat /etc/passwd` | 400 — blocked |</p>
<p>The legacy mode (no `SecurityConfig` detection attributes) sk…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-w7wg-6q7v-44f2"/>
  </entry>
</feed>
