{"answers":{"affected":"5 open source packages ship an affected version, including github.com/envoyproxy/envoy and envoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26330 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-26330 is a medium-severity use after free vulnerability in Envoyproxy Envoy, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26330 and fix it if it is affected.\n\nWhat it is: CVE-2026-26330 is a medium-severity use after free vulnerability in Envoyproxy Envoy, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26330 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/envoyproxy/envoy (Go): affected all versions; no fix listed\n- github.com/envoyproxy/envoy (Go): affected all versions; no fix listed\n- github.com/envoyproxy/envoy (Go): affected from 1.36.0 up to 1.36.4; no fix listed\n- github.com/envoyproxy/envoy (Go): affected from 1.36.0 up to 1.36.4; no fix listed\n- envoy (Bitnami): affected all versions; fixed in 1.34.13, 1.35.9, 1.36.5, 1.37.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-2026-26330/ (Markdown: https://insights.sbomify.com/CVE-2026-26330/index.md)","id":"CVE-2026-26330","markdown":"https://insights.sbomify.com/CVE-2026-26330/index.md","name":"CVE-2026-26330","record":{"aliases":["BIT-envoy-2026-26330","GHSA-c23c-rp3m-vpg3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Envoy proxy","requires_auth":"low_privilege","summary":"Attackers can crash Envoy proxy by triggering a use-after-free in the rate limit filter when response phase limits are enabled and fail.","user_interaction":"not_required","vuln_class":"use_after_free"},"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:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, At the rate limit filter, if the response phase limit with apply_on_stream_done in the rate limit configuration is enabled and the response phase limit request fails directly, it may crash Envoy. When both the request phase limit and response phase limit are enabled, the safe gRPC client instance will be re-used for both the request phase request and response phase request. But after the request phase request is done, the inner state of the request phase limit request in gRPC client is not cleaned up. When a second limit request is sent at response phase, and the second limit request fails directly, the previous request's inner state may be accessed and result in crash. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.","ecosystems":["Bitnami","Go"],"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's global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly","id":"CVE-2026-26330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"use_after_free","year":"2026"},"n_packages":5,"n_references":1,"next":{"headline":"yt-dlp: Arbitrary Command Injection when using the `--netrc-cmd` option","id":"CVE-2026-26331"},"packages":[{"ecosystem":"Bitnami","fixed":["1.34.13","1.35.9","1.36.5","1.37.1"],"introduced":["0","1.35.0","1.36.0","1.37.0"],"last_affected":[],"package":"envoy","purl":"pkg:bitnami/envoy","source":"BIT-envoy-2026-26330"},{"ecosystem":"Go","fixed":[],"introduced":[],"last_affected":[],"package":"github.com/envoyproxy/envoy","purl":null,"source":"GHSA-c23c-rp3m-vpg3"},{"ecosystem":"Go","fixed":[],"introduced":[],"last_affected":[],"package":"github.com/envoyproxy/envoy","purl":"pkg:golang/github.com/envoyproxy/envoy","source":"GHSA-c23c-rp3m-vpg3"},{"ecosystem":"Go","fixed":[],"introduced":["1.36.0"],"last_affected":["1.36.4"],"package":"github.com/envoyproxy/envoy","purl":null,"source":"GHSA-c23c-rp3m-vpg3"},{"ecosystem":"Go","fixed":[],"introduced":["1.36.0"],"last_affected":["1.36.4"],"package":"github.com/envoyproxy/envoy","purl":"pkg:golang/github.com/envoyproxy/envoy","source":"GHSA-c23c-rp3m-vpg3"}],"prev":{"headline":"OpenClaw has a path traversal in browser upload allows local file read","id":"CVE-2026-26329"},"products":["envoy"],"published":"2026-03-10","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-10","vendors":["envoyproxy"]},"summary":"Attackers can crash Envoy proxy by triggering a use-after-free in the rate limit filter when response phase limits are enabled and fail.","url":"https://insights.sbomify.com/CVE-2026-26330/"}