Bug 2577566 (CVE-2026-133577) - 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
Summary: CVE-2026-133577 github.com/kuadrant/kuadrant-operator: github.com/Kuadrant/wa...
Keywords:
Status: NEW
Alias: CVE-2026-133577
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 05:11 UTC by OSIDB Bzimport
Modified: 2026-11-20 06:57 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 05:11:52 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.