CVE-2026-121619 is an authentication bypass vulnerability in the Symfony FrameworkBundle and HttpFoundation components. It arises from trusting remote clients as reverse proxies when using the private_ranges shortcut in trusted proxy settings, allowing attackers to spoof client IP address, host, and scheme. This affects Symfony FrameworkBundle versions 7.1 prior to 7.4.23 and 8.x prior to 8.1.11, and HttpFoundation versions 7.2 prior to 7.4.23 and 8.x prior to 8.1.11. The flaw enables attackers to bypass IP allow lists, rate limiting, and audit logs, and to poison URLs in emails and caches. The issue is fixed in versions 7.4.23 and 8.1.11.
Action Pack is a framework for handling and responding to web requests. From 8.1 until 8.1.4.1, Since Rails 8.1.0, ActionDispatch::RemoteIp derives request.remote_ip from Rack::Request#forwarded_for, which under Rack 3 reads the RFC 7239 Forwarded header in preference to X-Forwarded-For. When a reverse proxy appends the client address to X-Forwarded-For but passes a client-supplied Forwarded header through unchanged, request.remote_ip returns an address chosen by the client, and the IP spoofing check does not raise, because it compares only Client-Ip with the forwarded addresses. An unauthenticated attacker could therefore spoof request.remote_ip, possibly bypassing IP-based access controls and rate limits keyed on the client address (including the default by: of rate_limit), and falsifying the client address in logs. An application is affected if it meets all of these requirements: Runs Rails 8.1.0 through 8.1.4 with Rack 3. Under Rack 2.2, forwarded_for reads only X-Forwarded-For. Is served behind a proxy that does not remove or overwrite a client-supplied Forwarded header. Relies on request.remote_ip for access control, rate limiting, or auditing. The fix detects a spoofed Forwarded header only when the proxy also sets X-Forwarded-For. An application whose proxy passes a client-supplied Forwarded header through and sets no X-Forwarded-For remains exposed after upgrading, and should configure the proxy to remove or overwrite Forwarded, or apply the workaround below. This issue is fixed in version 8.1.4.1.
CVE-2026-123339 is a vulnerability in Symfony HttpKernel that allows remote attackers to manipulate the host, scheme, and port of absolute URLs generated during a request. This occurs due to improper trust of forwarded headers in RouterListener::onKernelFinishRequest() when handling inline fragments, temporarily trusting 127.0.0.1 as a proxy. Applications accessed over HTTP from 127.0.0.1 behind certain proxies that forward client headers are affected. The issue is fixed in Symfony versions 5.4.56, 6.4.50, 7.4.23, and 8.1.11.
Remark42 versions from 1.0.0 up to but not including 1.16.2 improperly trust certain HTTP headers (True-Client-IP, X-Real-IP, X-Forwarded-For) without verifying if the source is a trusted proxy. This allows remote attackers to spoof IP addresses, bypass vote de-duplication, mint anonymous identities, and poison stored comment IPs and logs. The vulnerability is fixed in version 1.16.2, which introduces configuration for trusted proxies to mitigate the issue.
ezBookkeeping versions from 0.10.0 up to but not including 1.6.0 have a vulnerability where the Gin router is constructed without setting trusted proxies. This causes the application to trust spoofed X-Forwarded-For headers, allowing an unauthenticated attacker to bypass IP-based allowlists for certain protected actions. Although a valid MCP or API token is still required, the spoofed IP is logged and stored, misattributing activity to trusted hosts. The issue is fixed in version 1.6.0.
CGI versions prior to 5.00 for Perl trust the client-supplied X-Forwarded-Host header without validation in several URL-related functions. This allows an attacker to manipulate URLs used for redirects, links, and scripts, potentially poisoning shared caches and causing users to be redirected to attacker-controlled hosts.
Echo, a Go web framework, has a vulnerability in versions 5.0.0 through 5.4.0 where the ExtractIPFromRealIPHeader function trusts the client-supplied X-Real-IP header without properly validating the network peer. This allows an attacker to spoof the client IP address by supplying a loopback or private address, potentially bypassing IP-based allowlists, rate limiting, audit logs, or forwarding header protections. The issue is fixed in version 5.4.1.
A vulnerability in GitLab EE versions from 17.8 up to but not including 19.3.6, 19.4 up to but not including 19.4.3, and 19.5 up to but not including 19.5.1 allowed authenticated users to access paid AI features without a valid subscription. This was due to insufficient server-side validation in billing eligibility checks. The issue has been fixed in versions 19.3.6, 19.4.3, and 19.5.1.
CVE-2026-114474 is a vulnerability in Progressive Robot Ltd's hMailServer versions 6.0.0 through 6.3.6. It involves the use of a less trusted source for the envelope sender address during external-account mail downloads. This flaw allows a remote unauthenticated attacker to send mail that appears to originate from a domain hosted by the server, passing SPF and DMARC checks at receiving servers. The issue arises because the server uses the From header of downloaded messages as the envelope sender without proper validation, enabling spoofing of the envelope sender address.
CVE-2026-114437 is a medium severity vulnerability in the Go Chi web framework affecting versions before 5.4.0. The ClientIPFromXFF middleware incorrectly trusts the X-Forwarded-For header without verifying that the direct TCP peer address belongs to a configured trusted CIDR. This allows a client connecting directly to the server to spoof the client IP by appending a trusted proxy address, potentially misleading IP-based access controls or logging.
CVE-2026-107567 is a vulnerability in Progressive Robot Ltd's hMailServer versions 6.0.0 through 6.3.6 involving improper DKIM signing. The server signs outbound mail with the DKIM key of a hosted domain based solely on the From header without verifying sender authentication. This allows remote unauthenticated attackers to send mail that appears legitimately signed by the domain, potentially bypassing DKIM and DMARC protections. Exploitation requires DKIM signing to be enabled and mail forwarding or aliasing to external recipients.
Wheels versions prior to 4.1.2 have a vulnerability where the default production error-email address is derived from the Host header of the request that starts the application. If no explicit error-email recipient is set and the server accepts an attacker-controlled Host header, an attacker can cause error emails to be sent to an address they control. These emails may disclose error details, request metadata, and potentially sensitive configuration secrets and session data depending on the engine version. This issue is fixed in version 4.1.2.
CVE-2026-110726 affects Eclipse Connected Services Platform's api-gateway component up to version 1.7.3. The default rate-limit key resolver uses the leftmost element of the X-Forwarded-For header, which is attacker-controlled and not validated against trusted proxies. This allows attackers to bypass request-rate limiting by using unique header values to create unlimited independent rate-limit buckets.
CVE-2026-93483 is a critical vulnerability in Znuny versions before 6.5.25 and 7.3.7 that allows attackers to bypass authentication by manipulating the Remote-User HTTP header. This flaw arises because the application trusts the Remote-User header, enabling attackers to impersonate any user, including administrators, without a password. The vulnerability affects the HTTPBasicAuth modules used for agent and customer login interfaces. A fix is available in Znuny versions 6.5.25 and 7.3.7.
Dell Secure Connect Gateway (SCG) Policy Manager versions prior to 5.34.00.16 contain a vulnerability classified as CWE-348 (Use of Less Trusted Source). This flaw allows an unauthenticated remote attacker to potentially tamper with information. The vulnerability has a low severity with a CVSS score of 3.7. No known exploits are reported in the wild, and no patch information is provided.
CVE-2026-105051 is a low-severity vulnerability in Irdeto's Denuvo Anti-Tamper product up to version 2026-03-04. It allows bypassing a hypervisor presence check through CPUID interception using specific drivers on AMD and Intel platforms. The vulnerability does not impact confidentiality or availability but may allow limited integrity compromise.
PyJWT versions from 2.1.0 up to but not including 2.15.0 contain a vulnerability in the OKPAlgorithm.from_jwk function where the private JWK import does not verify that the public key component x corresponds to the private key component d. This can lead to a mismatch between the identity derived from x and operations performed with d. If an integration accepts private key parameters from a proof header without rejecting them, an attacker could misuse a stolen sender-constrained token without possessing the legitimate private key. The issue is fixed in version 2.15.0.
vLLM is an inference and serving engine for large language models. In versions from 0.22.1 through 0.28.0, the operator-supplied model revision pin (--revision / --code-revision) is not propagated to several Hugging Face artifact loads for the FunAudioChat and Tarsier2 architectures: the WhisperFeatureExtractor and speech_tokenizer PreTrainedTokenizerFast loads in vllm/model_executor/models/funaudiochat.py and the Qwen2VLConfig.from_pretrained call used by Tarsier2ProcessingInfo in vllm/model_executor/models/qwen2_vl.py. As a result, deployments pinned to a reviewed revision still resolve these behavior-affecting processor, tokenizer, and config artifacts from the repository's default revision, so a later change to the upstream default branch can alter audio preprocessing, speech tokenizer behavior, or Tarsier2 configuration without any change to the operator's configured pin. This is a supply-chain integrity and reproducibility failure for pinned deployments; it is residual to the earlier fix tracked as GHSA-3ww4-5jv9-j5gm / CVE-2026-47155 and does not constitute remote code execution or a trust_remote_code=False bypass. The issue is fixed in version 0.28.0.
The wpForo Forum WordPress plugin from 3.0.0 before 3.1.6 does not verify the source of client-supplied IP address headers before using them to key its per-visitor rate limit on paid AI requests, allowing unauthenticated attackers to bypass the limit by spoofing the header and exhaust the site owner's metered AI credits.
CVE-2026-97404 is a critical vulnerability in OpenStack Zaqar before version 22.0.2 affecting deployments using the WSGI transport with an authentication strategy. It allows an unauthenticated remote attacker who knows a target project's UUID to bypass Keystone authentication and pre-signed URL verification by sending a request with an empty URL-Signature header. This enables unauthorized reading, enumeration, creation, and deletion of that project's queues, messages, claims, and subscriptions. If the attacker claims an administrative role, they may perform administrative operations such as managing pools and flavors in admin_mode deployments. The websocket transport is not affected.