Skip to main content
Menu
CVEs

Red Hat Connectivity Link 1 authentication bypass in Kuadrant WASM shim

Affects the Kuadrant WASM shim in Red Hat Connectivity Link 1.5 when a TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy. The facts name no fixed version or patch ids.

CVE-2026-133577Published , updated

7.7HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

Red Hat Connectivity Link and Red Hat OpenShift AI are affected by a flaw in the Kuadrant WebAssembly shim that lets an attacker remotely, without logging in, send requests that skip authentication and rate limiting. When a TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy, unauthenticated requests are forwarded upstream and return 200 OK instead of 401, while both policies still report Enforced.

Written by a model

Original description

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.

Who should check

Teams running Red Hat Connectivity Link 1.5 (Kuadrant) with an AuthPolicy plus a TokenRateLimitPolicy, or a Gateway-level RateLimitPolicy with defaults or overrides, on the same routes.

“A flaw was found in the Kuadrant WebAssembly (WASM) shim shipped in Red Hat Connectivity Link 1.5.”

access.redhat.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects the Kuadrant WASM shim in Red Hat Connectivity Link 1.5. A TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy. Or a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of such routes.
  2. Workaround: Do not attach a TokenRateLimitPolicy to HTTPRoutes protected by an AuthPolicy, and do not attach a RateLimitPolicy with defaults or overrides to a Gateway or listener whose routes carry a TokenRateLimitPolicy. Use a route-level request-based RateLimitPolicy instead.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133577 (Github.com/kuadrant/kuadrant-operator: github.com/kuadrant/wasm-shim: kuadrant-operator: authpolicy is silently bypassed (fail-open) when…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133577 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat Connectivity Link 1: version range not reported
- Red Hat Red Hat Connectivity Link 1: version range not reported
- Red Hat Red Hat Connectivity Link 1: version range not reported
- Red Hat Red Hat Connectivity Link 1: version range not reported
- Red Hat Red Hat OpenShift AI (RHOAI): version range not reported
- Red Hat Red Hat OpenShift AI (RHOAI): version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects the Kuadrant WASM shim in Red Hat Connectivity Link 1.5. (source: https://access.redhat.com/security/cve/cve-2026-133577)
- A TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy. (source: https://access.redhat.com/security/cve/cve-2026-133577)
- Or a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of such routes. (source: https://access.redhat.com/security/cve/cve-2026-133577)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Do not attach a TokenRateLimitPolicy to HTTPRoutes protected by an AuthPolicy, and do not attach a RateLimitPolicy with defaults or overrides to a Gateway or listener whose routes carry a TokenRateLimitPolicy. Use a route-level request-based RateLimitPolicy instead. (source: https://www.cve.org/CVERecord?id=CVE-2026-133577)
CISA KEV: CVE-2026-133577 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133577 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2577566
- https://access.redhat.com/security/cve/CVE-2026-133577
- https://www.cve.org/CVERecord?id=CVE-2026-133577
- https://access.redhat.com/security/cve/cve-2026-133577
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133577
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133577"}.

Affected versions

cve.now Index

35Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach10/20Shipped in major Linux distributions
  • Severity7.7/10CVSS 7.7
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133577
RecordNVD · CVE-2026-133577
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2577566
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-133577

Questions about CVE-2026-133577

Is CVE-2026-133577 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Unauthenticated requests get 200 OK instead of 401, so requests are forwarded upstream without authentication, and rate limiting is not enforced either.

Source: access.redhat.com, cve.org

Am I affected, and how do I check?

The flaw is in the Kuadrant WASM shim shipped in Red Hat Connectivity Link 1.5. It applies 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. To check, look for these policy attachments on your HTTPRoutes, Gateways and listeners.

Source: access.redhat.com, cve.org

How do I fix CVE-2026-133577?

The facts name no fixed version or patch ids. The only step listed is to avoid the affected policy combinations until a fix is named.

Source: access.redhat.com, cve.org

What if there's no patch?

Do not attach a TokenRateLimitPolicy to HTTPRoutes protected by an AuthPolicy, and do not attach a RateLimitPolicy with defaults or overrides to a Gateway or listener whose routes carry a TokenRateLimitPolicy. Use a route-level request-based RateLimitPolicy instead.

Source: access.redhat.com, cve.org

No corrections so far. Something wrong on this page? Report an error.