{"uuid": "7d21caa4-7405-479f-95da-879ce3dc635d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-46821", "type": "seen", "source": "https://t.me/cvedetector/24764", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-46821 - Envoy URI Template Path Matching Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-46821 \nPublished : May 7, 2025, 10:15 p.m. | 29\u00a0minutes ago \nDescription : Envoy is a cloud-native edge/middle/service proxy. Prior to versions 1.34.1, 1.33.3, 1.32.6, and 1.31.8, Envoy's URI template matcher incorrectly excludes the `*` character from a set of valid characters in the URI path. As a result URI path containing the `*` character will not match a URI template expressions. This can result in bypass of RBAC rules when configured using the `uri_template` permissions. This vulnerability is fixed in Envoy versions v1.34.1, v1.33.3, v1.32.6, v1.31.8. As a workaround, configure additional RBAC permissions using `url_path` with `safe_regex` expression. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T00:52:37.000000Z"}