29 matches found
CVE-2026-110724
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110723
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110726
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110723
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110723
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
EUVD-2026-102030
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110723
In "api-gateway" versions till "1.7.3", The default rate-limit key resolver, "ClientIpKeyResolver", derives the per-client bucket key from the leftmost element of the "X-Forwarded-For" request header. That element is supplied by the originating HTTP client and is not validated against any...
CVE-2026-110723
The api-gateway software (versions up to 1.7.3 ) is vulnerable to a rate-limiting bypass because the default ClientIpKeyResolver retrieves the per-client bucket key from the leftmost element of the X-Forwarded-For request header. Since this element is provided by the client and is not validated a...
CVE-2026-110723
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110724
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110724
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110724
In "api-gateway" versions till "1.7.3", The default rate-limit key resolver, "ClientIpKeyResolver", derives the per-client bucket key from the leftmost element of the "X-Forwarded-For" request header. That element is supplied by the originating HTTP client and is not validated against any...
CVE-2026-110724
The api-gateway software, in versions up to 1.7.3 , is vulnerable to a rate-limiting bypass. The default ClientIpKeyResolver derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. Because this header is supplied by the client and is not validated agains...
EUVD-2026-102029
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110724
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110726
In "api-gateway" versions till "1.7.3", The default rate-limit key resolver, "ClientIpKeyResolver", derives the per-client bucket key from the leftmost element of the "X-Forwarded-For" request header. That element is supplied by the originating HTTP client and is not validated against any...
CVE-2026-110726
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
EUVD-2026-102022
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110726
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...
CVE-2026-110726
In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...