CVE-2026-133577: Github.com/kuadrant/kuadrant-operator: github.com/kuadrant/wasm-shim: kuadrant-operator: authpolicy is silently bypassed (fail-open) when a tokenratelimitpolicy is combined with an authpolicy or a gateway-level ratelimitpolicy
A flaw was found in the Kuadrant WebAssembly (WASM) shim shipped in Red Hat Connectivity Link 1.5. When a TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy - or when a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of such routes - the shim's action pipeline fails to dispatch the authentication guard at request time, and the request is forwarded upstream. Unauthenticated requests return 200 OK instead of 401, and neither authentication nor rate limiting is enforced. Both policies continue to report Enforced, leaving no status-level indication of the failure.
Other sources
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.
— Red Hat
Affected Software
Frequently Asked Questions
What capabilities does an attacker need to exploit this issue?
The vulnerability is remotely exploitable over the network and does not require attacker privileges or user interaction. Exploitation is rated as having high attack complexity.
What is the potential security impact if exploitation succeeds?
Successful exploitation can result in high impact to confidentiality and integrity, with low impact to availability. The scope is unchanged.