REDHAT-BUG-2577566: High severity Solo.io kgateway vulnerability

Published Nov 20, 2026
·
Updated

When a TokenRateLimitPolicy is applied alongside an AuthPolicy on the same HTTPRoute, unauthenticated requests unexpectedly return HTTP 200 instead of 401 and reach the backend. The same failure occurs when a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of a route carrying a TokenRateLimitPolicy. Configured rate limits (5/min and 10/min) are not enforced, even with a burst of 30 requests. Removing the TokenRateLimitPolicy restores the expected authentication behavior, while a regular request-based RateLimitPolicy correctly enforces both authentication (401) and rate limiting (429).

Gateway logs show Limitador response JSON parsing and CEL predicate evaluation errors. The suspected root cause is that a response-body store action prepended to the WASM action chain cannot settle during the request phase, leaving the authentication guard pending and preventing the auth check from being dispatched.

Affected Software

1 affected component
Solo.io kgateway

Event History

Nov 20, 2026
Data Sourced
via Red Hat·05:11 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which configurations are affected?

The issue occurs when a TokenRateLimitPolicy and an AuthPolicy are applied to the same HTTPRoute. It also occurs when a route with a TokenRateLimitPolicy is served by a Gateway or listener that has a RateLimitPolicy with defaults or overrides.

2

What is the practical security impact?

Unauthenticated requests can receive HTTP 200 and reach the backend instead of being rejected with HTTP 401. Configured token rate limits, including 5/min and 10/min limits, may also fail to enforce during a burst of requests.

3

How can I tell whether this issue is occurring?

Test an unauthenticated request to an affected route and check whether it returns HTTP 200 or reaches the backend rather than returning HTTP 401. Gateway logs may contain Limitador response JSON parsing errors and CEL predicate evaluation errors.

4

What mitigation is available if the affected policy combination cannot be patched immediately?

Removing the TokenRateLimitPolicy restores the expected authentication behavior. A regular request-based RateLimitPolicy correctly enforces authentication with HTTP 401 and rate limiting with HTTP 429.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203