Improper Null Termination Affecting openshift-service-mesh/proxyv2-rhel9 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.21% (12th 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-OPENSHIFTSERVICEMESHPROXYV2RHEL9-17810280
  • published3 Jul 2026
  • disclosed26 Jun 2026

Introduced: 26 Jun 2026

CVE-2026-47778  (opens in a new tab)
CWE-170  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 openshift-service-mesh/proxyv2-rhel9.

NVD Description

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

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, a structural flaw was identified in DefaultCertValidator::verifySubjectAltName where the extracted DNS SAN string is cast to a C-style string using .c_str() before being passed to the Utility::dnsNameMatch() algorithm. If the attacker serves a certificate with a dNSName SAN containing an embedded NUL byte, the helper Utility::generalNameAsString captures the complete string including the NUL. However, when .c_str() evaluates it, implicit conversion to absl::string_view inside dnsNameMatch relies on strlen(), prematurely truncating the evaluation context. Envoy evaluates trucated string against the exact required config_san match and returns true, thereby successfully validating the string with the Nul byte for an upstream routing. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.

CVSS Base Scores

version 3.1