Guard Core: Unvalidated X-Forwarded-For-derived string used as a Redis key component and interpolated into a KEYS glob
Affects guard-coreSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 3.13.0 when convenient.
Data as of 19 Nov 2026, 23:23 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 3.13.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade guard-core to 3.13.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIguard-core | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Guard Core version 3.13.0. Users should upgrade to this version or later. The fix includes validating the extracted X-Forwarded-For entry using ipaddress.ip_address() and falling back to the connecting IP if validation fails. It also escapes glob metacharacters in strings interpolated into Redis KEYS patterns or replaces the KEYS command with more efficient atomic counters or Lua scripts. Deployments with default settings (empty trusted_proxies) are not vulnerable and require no action. No additional mitigations are recommended beyond applying the official fix.
Description
Guard Core versions prior to 3.13.0 contain a vulnerability where the X-Forwarded-For (XFF) header is extracted without IP address validation and used directly in Redis key names and KEYS glob patterns. This allows attacker-controlled strings to cause cross-client counter contamination, unbounded Redis key growth, blocking Redis scans, and potential server errors due to unhandled exceptions. The issue affects deployments where the extracted XFF entry is attacker-controllable and trusted proxies are configured. No data exposure is reported. A fix is available in version 3.13.0 that validates the IP and escapes glob metacharacters or replaces the KEYS command usage.
References
- github.com/Guard-Core/guard-core/security/advisories/GHSA-gm9r-hvc9-96gv (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129304 (opens in a new tab)
- github.com/Guard-Core/guard-core/pull/68 (opens in a new tab)
- github.com/Guard-Core/guard-core/commit/c07239fa1c5aa93e3f179440e79dad652977d3e4 (opens in a new tab)
- github.com/Guard-Core/guard-core/releases/tag/3.13.0 (opens in a new tab)
- github.com/rennf93/guard-core (opens in a new tab)