{"answers":{"affected":"1 open source package ship an affected version, including envoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46821 in the wild and no public exploit code.","fix":"Upgrade envoy to a fixed version for your release line: 1.31.8, 1.32.6, 1.33.3 or 1.34.1.","what":"CVE-2025-46821 is a medium-severity vulnerability in Envoyproxy Envoy, published on 7 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46821 and fix it if it is affected.\n\nWhat it is: CVE-2025-46821 is a medium-severity vulnerability in Envoyproxy Envoy, published on 7 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-46821 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- envoy (Bitnami): affected all versions; fixed in 1.31.8, 1.32.6, 1.33.3, 1.34.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46821/ (Markdown: https://insights.sbomify.com/CVE-2025-46821/index.md)","id":"CVE-2025-46821","markdown":"https://insights.sbomify.com/CVE-2025-46821/index.md","name":"CVE-2025-46821","record":{"aliases":["BIT-envoy-2025-46821","GHSA-c7cm-838g-6g67"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Envoy proxy","requires_auth":"none","summary":"Attackers can bypass RBAC rules in Envoy by using asterisks in URI paths, requiring specific RBAC configurations to exploit.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"envoy","vendor":"envoyproxy"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-186","name":"Overly Restrictive Regular Expression"}],"description":"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Envoy vulnerable to bypass of RBAC uri_template permission","id":"CVE-2025-46821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"security_feature_bypass","year":"2025"},"n_packages":1,"n_references":1,"next":{"headline":"Unauthenticated Arbitrary File Read via Absolute Path","id":"CVE-2025-46822"},"packages":[{"ecosystem":"Bitnami","fixed":["1.31.8","1.32.6","1.33.3","1.34.1"],"introduced":["0","1.32.0","1.33.0","1.34.0"],"last_affected":[],"package":"envoy","purl":"pkg:bitnami/envoy","source":"BIT-envoy-2025-46821"}],"prev":{"headline":"phpgt/Dom exposes the GITHUB_TOKEN in Dom workflow run artifact","id":"CVE-2025-46820"},"products":["envoy"],"published":"2025-05-07","related":[{"cvss_score":10,"headline":"Trivial authentication bypass in Envoy","id":"CVE-2022-29226","kev_date_added":null,"published":"2022-06-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-18801","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-18802","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2020-35470","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.6,"headline":"Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata","id":"CVE-2024-23324","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":8.6,"headline":"Envoy vulnerable to OAuth2 credentials exploit with permanent validity","id":"CVE-2023-35941","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":8.6,"headline":"Incorrect handling of H2 GOAWAY + SETTINGS frames","id":"CVE-2021-39162","kev_date_added":null,"published":"2021-09-09"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-08","vendors":["envoyproxy"]},"summary":"Attackers can bypass RBAC rules in Envoy by using asterisks in URI paths, requiring specific RBAC configurations to exploit.","url":"https://insights.sbomify.com/CVE-2025-46821/"}