Lucene search
+L

10 matches found

NVD
NVD
•added 2026/10/15 1:17 p.m.•6 views

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

SaveExploits0References3
NVD
NVD
•added 2026/10/15 1:17 p.m.•4 views

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

7.5CVSS
SaveExploits0References3
NVD
NVD
•added 2026/10/15 12:16 p.m.•8 views

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

6.5CVSS
SaveExploits0References3
CVE
CVE
•added 2026/10/15 12:14 p.m.•11 views

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

7.5CVSS5.7AI score
SaveExploits0References3
Cvelist
Cvelist
•added 2026/10/15 12:14 p.m.•16 views

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

SaveExploits0References3
EUVD
EUVD
•added 2026/10/15 12:14 p.m.•5 views

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

7.5CVSS5.7AI score
SaveExploits0References3
CVE
CVE
•added 2026/10/15 12:11 p.m.•15 views

CVE-2026-110724

The api-gateway software (versions up to 1.7.3 ) contains a vulnerability in the default rate-limit key resolver, ClientIpKeyResolver . The component derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header without validating it against a trusted-proxy lis...

5.7AI score
SaveExploits0References3
EUVD
EUVD
•added 2026/10/15 12:11 p.m.•5 views

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

5.7AI score
SaveExploits0References3
Cvelist
Cvelist
•added 2026/10/15 11:58 a.m.•15 views

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

SaveExploits0References3
EUVD
EUVD
•added 2026/10/15 11:58 a.m.•4 views

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

6.5CVSS5.7AI score
SaveExploits0References3
Rows per page
Query Builder