{"id":"CVE-2026-73551","aliases":["BIT-envoy-2026-73551","EUVD-2026-84119","GHSA-2w8w-rfw7-8gg4","openSUSE-SU-2026:11630-1"],"status":"published","title":"Envoy: Path normalization does not handle dot and dotdot segments with parameters","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","severity":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00527,"percentile":0.4511,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-647"],"published":"2026-08-28T00:00:00Z","modified":"2026-10-28T11:23:05Z","fixes":[{"ecosystem":"Bitnami","package":"envoy","fixed_in":["1.36.10","1.37.6","1.38.4","1.39.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.36.10"},{"introduced":"1.37.0"},{"fixed":"1.37.6"},{"introduced":"1.38.0"},{"fixed":"1.38.4"},{"introduced":"1.39.0"},{"fixed":"1.39.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"istioctl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.30.4-1.1"}]}],"bundled":13}],"products":[{"vendor":"envoyproxy","product":"envoy"}],"references":[{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-2w8w-rfw7-8gg4","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory"]},{"url":"https://github.com/envoyproxy/envoy/commit/28b6d60a6d96edeece121cac5be701eb46cc7f24","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/envoyproxy/envoy/commit/d40a68b0a30a003c4e0a9fd3af637f828b52c37b","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/envoyproxy/envoy/commit/e9d6c329f9a3ff19432bf39b60c601df7e3eda33","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/envoyproxy/envoy/commit/f74d1107c4f5c9679b66f7a03a6c5b75ddde1989","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/envoyproxy/envoy/releases/tag/v1.36.10","tags":["x_refsource_MISC","Release Notes","article","web"]},{"url":"https://github.com/envoyproxy/envoy/releases/tag/v1.37.6","tags":["x_refsource_MISC","Release Notes","article","web"]},{"url":"https://github.com/envoyproxy/envoy/releases/tag/v1.38.4","tags":["x_refsource_MISC","Release Notes","article","web"]},{"url":"https://github.com/envoyproxy/envoy/releases/tag/v1.39.1","tags":["x_refsource_MISC","Release Notes","article","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-73551","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/73xxx/CVE-2026-73551.json","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73553","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-73551","title":"Envoy: Path normalization does not handle dot and dotdot segments with parameters","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","status":"published","published":"2026-09-21T20:17:02.62Z","modified":"2026-09-28T20:41:32.313Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-647"],"updated_at":"2026-11-02T13:43:33.766176Z"}],"euvd":[{"id":"EUVD-2026-84119","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","status":"published","published":"2026-09-21T20:17:02Z","modified":"2026-09-28T20:41:32Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T17:27:52.759804Z"}],"nvd":[{"id":"CVE-2026-73551","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","status":"published","published":"2026-09-21T21:17:09.473Z","modified":"2026-10-05T14:06:32.38Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-647"],"updated_at":"2026-11-02T14:12:50.368368Z"}],"osv":[{"id":"CVE-2026-73551","title":"Envoy: Path normalization does not handle dot and dotdot segments with parameters","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","status":"published","published":"2026-09-21T20:17:02.62Z","modified":"2026-10-28T11:23:05.337598876Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-647"],"updated_at":"2026-11-02T15:45:16.365946Z"},{"id":"BIT-envoy-2026-73551","title":"Envoy: Path normalization does not handle dot and dotdot segments with parameters","description":"Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.","status":"published","published":"2026-09-29T08:43:16.381Z","modified":"2026-10-06T15:15:04.562355687Z","updated_at":"2026-11-02T15:28:29.563843Z"},{"id":"openSUSE-SU-2026:11630-1","title":"istioctl-1.30.4-1.1 on GA media","description":"These are all security issues fixed in the istioctl-1.30.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-28T00:00:00Z","modified":"2026-08-29T09:15:04.355652515Z","updated_at":"2026-11-02T16:58:39.516824Z"}]}}