{"cve":{"cve_id":"CVE-2026-48090","is_kev":false,"kev_date_added":null,"kev_vendor_project":null,"kev_product":null,"kev_vulnerability_name":null,"kev_short_description":null,"kev_required_action":null,"kev_due_date":null,"kev_known_ransomware":null,"kev_notes":null,"kev_cwes":null,"epss_score":null,"epss_percentile":null,"epss_as_of":null,"description":"Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.37.0 until 1.37.5 and 1.38.3, the HTTP OAuth2 filter (envoy.filters.http.oauth2) can leave an in-flight async token exchange attached to a downstream stream that has already been torn down. A late AsyncClient completion can still invoke OAuth2Filter methods that use StreamDecoderFilterCallbacks after that object’s lifetime has ended, causing undefined behavior, worker crashes (availability loss), and use-after-free / invalid-vptr failures under AddressSanitizer. This is a memory-safety / lifetime issue in the data plane, not a trivial config bug. Remote code execution is not claimed here; the primary demonstrated impact is DoS via crash and UB; any further impact would be deployment- and allocator-dependent.  This vulnerability is fixed in 1.37.5 and 1.38.3.","published_at":"2026-06-26T18:03:05.257000Z","last_modified_at":null,"cvss_v3_score":5.9,"cvss_v3_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","cvss_v3_severity":"MEDIUM","cvss_v4_score":null,"cvss_v4_vector":null,"cvss_v4_severity":null,"ssvc_decision":null,"ssvc_exploitation":null,"ssvc_automatable":null,"ssvc_technical_impact":null,"cwes":["CWE-416"],"nvd_references":["https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f"],"vuln_status":null,"trending_score":null,"is_trending":false,"has_trended":false,"trended_number_one":false,"trending_peak_score":null,"trending_peak_rank":null,"started_trending_at":null,"trended_number_one_at":null,"summary_generated":null,"summary_generated_at":null,"summary_model":null,"created_at":"2026-06-28T17:55:03.830140Z","updated_at":"2026-06-28T23:30:42.802049Z"},"effective_severity":"MEDIUM","badges":[],"impact_analysis":[],"cvss_v3_decoded":{"version":"3.1","metrics":[{"metric":"AV","name":"Attack Vector","value":"N","value_label":"Network"},{"metric":"AC","name":"Attack Complexity","value":"H","value_label":"High"},{"metric":"PR","name":"Privileges Required","value":"N","value_label":"None"},{"metric":"UI","name":"User Interaction","value":"N","value_label":"None"},{"metric":"S","name":"Scope","value":"U","value_label":"Unchanged"},{"metric":"C","name":"Confidentiality","value":"N","value_label":"None"},{"metric":"I","name":"Integrity","value":"N","value_label":"None"},{"metric":"A","name":"Availability","value":"H","value_label":"High"}]},"cvss_v4_decoded":{"version":null,"metrics":[]},"affected":[{"vendor_slug":"envoyproxy","vendor_name":"envoyproxy","product_slug":"envoy","product_name":"envoy","version_start":">= 1.38.0, < 1.38.3","version_start_inclusive":true,"version_end":">= 1.38.0, < 1.38.3","version_end_inclusive":true,"cpe23_uri":"cve5:envoyproxy:envoy:>= 1.38.0, < 1.38.3:>= 1.38.0, < 1.38.3"},{"vendor_slug":"envoyproxy","vendor_name":"envoyproxy","product_slug":"envoy","product_name":"envoy","version_start":">= 1.37.0, < 1.37.5","version_start_inclusive":true,"version_end":">= 1.37.0, < 1.37.5","version_end_inclusive":true,"cpe23_uri":"cve5:envoyproxy:envoy:>= 1.37.0, < 1.37.5:>= 1.37.0, < 1.37.5"}],"exploit_refs":[],"news":[],"references":[{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f","source_type":"VENDOR_ADVISORY","tags":["advisory"]}],"timeline":[{"type":"published","at":"2026-06-26T18:03:05.257000Z","label":"CVE published","source":null}]}