How many CVEs have patched rewritePathHeader?

1 published CVEs changed rewritePathHeader in envoyproxy/envoy, in 2 distinct patches totalling 2 changed lines, between 2026 and 2026.

What is the latest CVE that changed rewritePathHeader?

CVE-2026-73511 (Envoy: Potential path-matching/authentication bypass when using Envoy in combination with a backend stripping per-segment path (matrix) parameters (e.g. Apache Tomcat)), published 2026-09-21, changed lines 1370 of source/common/router/config_impl.cc.

How does rewritePathHeader compare to the rest of envoyproxy/envoy?

envoyproxy/envoy has 44 CVEs with a located fix in total; 1 of them changed rewritePathHeader.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

envoyproxy/envoy

Function

rewritePathHeader

Name: rewritePathHeader in envoyproxy/envoy: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

source/common/router/config_impl.cc

Last patched September 21, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

rewritePathHeader in envoyproxy/envoy was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 2 lines in total.

envoyproxy/envoy has 44 CVEs with a located fix in total, so 2% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed rewritePathHeader, newest first, with the lines each fix touched.

Envoy: Potential path-matching/authentication bypass when using Envoy in combination with a backend stripping per-segment path (matrix) parameters (e.g. Apache Tomcat)
CVE-2026-73511 · line 1370 · +1 −1
Medium · CVSS 5.3
EPSS 0.4%2026-09-21

Get an alert when the next CVE fix lands in envoyproxy/envoy, with the patched functions.

Monitor envoy CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in envoyproxy/envoy changed by the most CVE fixes.

MessageDone3 CVEs · source/common/http/http1/balsa_parser.cc decodeHeaders2 CVEs · source/common/http/conn_manager_impl.cc saw_downstream_reset_2 CVEs · source/common/http/filter_manager.h maybeEndDecode2 CVEs · source/common/http/filter_manager.cc bufferedData2 CVEs · source/common/http/filter_manager.cc sendProtocolError2 CVEs · source/common/http/http1/codec_impl.cc

All patched functions in envoyproxy/envoy

Frequently asked questions

Common questions about CVE fixes to rewritePathHeader.

How many CVEs have patched rewritePathHeader?: 1 published CVEs changed rewritePathHeader in envoyproxy/envoy, in 2 distinct patches totalling 2 changed lines, between 2026 and 2026.
What is the latest CVE that changed rewritePathHeader?: CVE-2026-73511 (Envoy: Potential path-matching/authentication bypass when using Envoy in combination with a backend stripping per-segment path (matrix) parameters (e.g. Apache Tomcat)), published 2026-09-21, changed lines 1370 of source/common/router/config_impl.cc.
How does rewritePathHeader compare to the rest of envoyproxy/envoy?: envoyproxy/envoy has 44 CVEs with a located fix in total; 1 of them changed rewritePathHeader.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track envoyproxy/envoy CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing