Protection Mechanism Failure Affecting openshift-service-mesh/istio-operator-bundle package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.31% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-OPENSHIFTSERVICEMESHISTIOOPERATORBUNDLE-14516624
  • published18 Dec 2025
  • disclosed3 Dec 2025

Introduced: 3 Dec 2025

CVE-2025-64763  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 openshift-service-mesh/istio-operator-bundle.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openshift-service-mesh/istio-operator-bundle package and not the openshift-service-mesh/istio-operator-bundle package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Envoy is a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, when Envoy is configured in TCP proxy mode to handle CONNECT requests, it accepts client data before issuing a 2xx response and forwards that data to the upstream TCP connection. If a forwarding proxy upstream from Envoy then responds with a non-2xx status, this can cause a de-synchronized CONNECT tunnel state. By default Envoy continues to allow early CONNECT data to avoid disrupting existing deployments. The envoy.reloadable_features.reject_early_connect_data runtime flag can be set to reject CONNECT requests that send data before a 2xx response when intermediaries upstream from Envoy may reject establishment of a CONNECT tunnel.

CVSS Base Scores

version 3.1