CVE-2026-133577

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.

Statement

This issue is classified as Important severity because it allows unauthenticated access to any route protected by an AuthPolicy when a TokenRateLimitPolicy is also present on the route or a RateLimitPolicy with defaults or overrides is inherited from the Gateway - supported, non-default configurations that are the standard pattern for metered APIs, the product's primary use case. Exploitation is trivial and deterministic: an ordinary unauthenticated request is forwarded to the backend with no credentials required.

Mitigation

To mitigate this issue, do not attach a TokenRateLimitPolicy to HTTPRoutes that are protected by an AuthPolicy, and do not attach a RateLimitPolicy with defaults or overrides to a Gateway or listener whose routes carry a TokenRateLimitPolicy. Enforce request limits with a route-level request-based RateLimitPolicy instead, which correctly enforces both authentication and rate limiting in this configuration. After any policy change, verify enforcement by sending requests to the route from outside the cluster without credentials and confirming they are rejected with HTTP 401.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.7N/A7.7
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactLowN/ALow

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Red Hat CVSS v3 Score Explanation

AC:H reflects the non-default (though supported and common for API metering) policy combination required on the target route; attacker-side exploitation is a trivial unauthenticated request. A:L accounts for rate limits also being disabled.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

An attacker could read sensitive data, either by reading the data directly from a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.

Integrity

Technical Impact: Modify Application Data; Modify Files or Directories

An attacker could modify sensitive data, either by writing the data directly to a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.

Access Control

Technical Impact: Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands

When access control checks are not applied consistently - or not at all - an attacker could gain privileges and execute unauthorized code or commands by modifying or reading critical data directly, or by accessing insufficiently-protected, privileged functionality.

Frequently Asked Questions

Want to get errata notifications? Sign up here.