CVE-2026-129304

Guard Core: Unvalidated X-Forwarded-For-derived string used as a Redis key component and interpolated into a KEYS glob pattern

Published Nov 16, 2026 CVSS 3.1 · 5.4 Medium 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, _extract_from_forwarded_header() in guard_core/utils.py returns the selected X-Forwarded-For entry without validating that it is an IP address. In deployments configured with trusted_proxies where the selected entry is attacker-controlled, the arbitrary client_ip string reaches BehaviorTracker in guard_core/handlers/behavior_handler.py and is interpolated into Redis key names and blocking KEYS glob patterns. Glob metacharacters can cause one request to count other clients' behavior events, embedded separators can disturb key parsing, and rotating identities can create unbounded keys while repeatedly scanning the shared Redis keyspace. A non-IP identity can also reach a ban action and cause an uncaught validation error. This issue is fixed in version 3.13.0.

Analysis

AI-generated

Technical impact

Guard‑Core, an API security framework, neglects to validate the value extracted from the X‑Forwarded‑For header. The unchecked string is incorporated into Redis key names and glob patterns, creating an avenue for an attacker to influence how the system records and evaluates client activity. This unchecked input can cause the application to count unrelated client requests, trigger bans for legitimate users, or force the server to scan an ever‑growing set of Redis keys. The flaw reflects CWE‑20, which concerns improper input validation and could degrade confidentiality, integrity, and availability of the protected services.

Affected Systems

Products affected include the rennf93 Guard‑Core library, from its initial release 1.0.0 through all versions prior to 3.13.0. The issue was addressed in the 3.13.0 release, which implements validation of the X‑Forwarded‑For value before it is used in Redis key construction.

Risk and Exploitability

The CVSS score of 5.4 indicates a medium severity risk. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The most likely attack vector is a remote HTTP request that supplies a malicious X‑Forwarded‑For header in environments where the application trusts that header. An attacker controlling this header can cause the system to misinterpret activity, potentially leading to denial of service or incorrect request throttling. The lack of a publicly disclosed exploit and the need for a specific configuration reduce the current exploitability to moderate.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Guard‑Core to version 3.13.0 or later to enable proper validation of X‑Forwarded‑For values.
  • If upgrading immediately is not feasible, configure the application to avoid trusting externally supplied X‑Forwarded‑For headers; disable or restrict the trusted_proxies setting so that request headers cannot be manipulated by clients.
  • Implement an additional IP address validation layer before any client identifier is used in Redis key construction, or use the canonical remote address supplied by the transport layer instead of the forwarded header.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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, _extract_from_forwarded_header() in guard_core/utils.py returns the selected X-Forwarded-For entry without validating that it is an IP address. In deployments configured with trusted_proxies where the selected entry is attacker-controlled, the arbitrary client_ip string reaches BehaviorTracker in guard_core/handlers/behavior_handler.py and is interpolated into Redis key names and blocking KEYS glob patterns. Glob metacharacters can cause one request to count other clients' behavior events, embedded separators can disturb key parsing, and rotating identities can create unbounded keys while repeatedly scanning the shared Redis keyspace. A non-IP identity can also reach a ban action and cause an uncaught validation error. This issue is fixed in version 3.13.0.
Title Guard Core: Unvalidated X-Forwarded-For-derived string used as a Redis key component and interpolated into a KEYS glob pattern
Weaknesses CWE-20
References
Metrics cvssV3_1

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

Subscriptions

No data.

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

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