Read the docs

Unvalidated X-Forwarded-For value used in Redis keys in Guard Core

Priority MEDIUM 40CWE-20Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

Guard Core from 1.0.0 before 3.13.0 accepts any selected X-Forwarded-For entry as a client identity. With trusted_proxies configured and an attacker-controlled entry, the value is interpolated into Redis keys and KEYS glob patterns, letting one request count other clients' events (CWE-20). A remote attacker without credentials can send such a header, and a non-IP identity can also cause an uncaught validation error on a ban.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Fix Fixed guard-core (rennf93): 3.13.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
rennf93guard-core1.0.0 to before 3.13.03.13.0Patch availableCNA
  • guard-core Vendorrennf93 Affected 1.0.0 to before 3.13.0 Fixed in 3.13.0 Patch available CNA

Remediation

Upgrade Guard Core to version 3.13.0, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA guard-core (rennf93) Fixed in 3.13.0

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-129304

References

  • TI-2025-34178 fastapi-guard patch contains bypassable RegEx CVSS 4.0HIGH 7.8
  • TI-2025-29447 FastAPI Guard Remote Header Injection via X-Forwarded-For Manipulation CVSS 3.1HIGH 7.5
  • TI-2025-33483 ReDoS in fastapi-guard's penetration attempts detector CVSS 4.0MEDIUM 6.9
  • TI-2026-92274 Guard Core whitespace collapsing disables CRLF detectors in default mode CVSS 3.1LOW 3.7
  • TI-2026-92273 Quadratic ReDoS in Guard Core built-in detection pattern freezes event loop CVSS 3.1HIGH 7.5

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences