Medium [CVE-2026-114437] client IP spoofing via unverified direct connection in ClientIPFromXFF middleware
This medium-severity Red Hat Linux advisory covers CVE-2026-114437; related products: Logging Subsystem for Red Hat OpenShift, Multicluster Engine for Kubernetes, OpenShift Pipelines.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Red Hat Linux RHEL & SELinux publishes the next one.
See Red Hat Linux RHEL & SELinux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
client IP spoofing via unverified direct connection in ClientIPFromXFF middleware. Red Hat rates this moderate (CVSS 4.8).
Weakness: CWE-346.
Affected products named by the advisory: Logging Subsystem for Red Hat OpenShift; Multicluster Engine for Kubernetes; OpenShift Pipelines; OpenShift Serverless; and 11 more.
Affected products named by the advisory: Red Hat Advanced Cluster Management for Kubernetes 2; Red Hat Enterprise Linux 8; Red Hat OpenShift Container Platform 4; Red Hat OpenShift Dev Spaces; and 7 more.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Mitigation checklist
- Restrict network exposure so that the application only accepts connections from trusted reverse proxies or load balancers, preventing direct client reachability: 1. Configure firewall rules on the host to only allow traffic from trusted proxy IP addresses to the application port: ``` firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_PROXY_IP> firewall-cmd --permanent --remove-port=<PORT>/tcp firewall-cmd --reload ``` 2. In OpenShift or Kubernetes environments, apply an Ingress NetworkPolicy ensuring pod endpoints only accept traffic from designated ingress router controllers. 3. Configure the upstream reverse proxy (e.g., Envoy, HAProxy, or NGINX) to strip or sanitize incoming X-Forwarded-For headers from untrusted external clients before routing requests to backend services. Caveats: Restricting direct access may interrupt client traffic if services were previously exposed directly without a proxy. Reloading firewalld with `firewall-cmd --reload` will briefly reapply filtering rules and may affect active network sessions.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
More Red Hat Linux advisories
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
- CVE-2026-53362Jul 4, 2026account for fraggap on the paged allocation path
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.