CVE-2026-73547

validated

GHSA-87ph-jqwm-pg6r ↗EUVD-2026-84110 ↗

check availablenot proven exploitable

cve.orgpublic poc−26dkev

envoy proxy:Envoy <1.40.0

fixed in 1.39.1, 1.38.4, 1.37.6, 1.36.10

CWE-20 Improper Input Validation

ETK-2026-761, permanent identifier

cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

+15dTTV

32mAI analysis

Check if you are vulnerable

timeline

0 = trigger signal

public poc−26dtrigger signal (cve.org) +0dcheck available+15dagent stopped

−20d

−10d

+10d

description

Envoy's ext_authz filter can allow an unauthenticated downstream client to terminate the proxy process. Affected deployments accept path-less CONNECT requests and use authorization responses that modify query parameters.

mitigation

Upgrade Envoy to 1.39.1, 1.38.4, 1.37.6, 1.36.10 or later.

fixed in 1.39.1, 1.38.4, 1.37.6, 1.36.10

check

available

exploit

automation

deterministic

auth required

EPSS

0.55%45th percentile

agent run time

32m

cve.org record, t = 0

2026-09-21 19:47Z

Δ to public poc

−26d

Δ to kev

–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-09-21 19:47Z
ghsa: trigger signal, started the run
https://github.com/envoyproxy/envoy/security/advisories/GHSA-87ph-jqwm-pg6r
2026-09-21 19:47Z
public poc, published 2026-08-26 14:02Z
https://github.com/envoyproxy/envoy/security/advisories/GHSA-87ph-jqwm-pg6r
2026-09-21 19:47Z
cve.org record for CVE-2026-73547
cve_org · https://www.cve.org/CVERecord?id=CVE-2026-73547

this entry in the feed

GET /api/v1/feed/CVE-2026-73547

{
  "etk_id": "ETK-2026-761",
  "cve_id": "CVE-2026-73547",
  "display_id": "CVE-2026-73547",
  "ghsa_id": "GHSA-87ph-jqwm-pg6r",
  "euvd_id": "EUVD-2026-84110",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Null pointer denial of service in Envoy ext_authz",
  "summary": "Envoy's ext_authz filter can allow an unauthenticated downstream client to terminate the proxy process. Affected deployments accept path-less CONNECT requests and use authorization responses that modify query parameters.",
  "mitigation": "Upgrade Envoy to 1.39.1, 1.38.4, 1.37.6, 1.36.10 or later.",
  "vendor": "envoy proxy",
  "product": "envoy proxy:Envoy",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<1.40.0"
      ],
      "ecosystem": "envoy proxy",
      "fixed_versions": [
        "1.39.1",
        "1.38.4",
        "1.37.6",
        "1.36.10"
      ],
      "package_name": "Envoy",
      "purl": null
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0055,
  "epss_percentile": 0.4518,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 32.05725126666667,
  "t0_at": "2026-09-21T19:47:54.720000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-06T13:04:54.994595+00:00",
      "days": 14.720142067071759,
      "is_lower_bound": false,
      "measured_at": "2026-09-21T19:47:54.720000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-08-26T14:02:53+00:00",
      "days": -26.239603240740742,
      "is_lower_bound": false,
      "measured_at": "2026-09-21T19:47:54.720000+00:00",
      "url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-87ph-jqwm-pg6r"
    },
    "trigger_signal": {
      "at": "2026-09-21T19:47:54.720000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-21T19:47:54.720000+00:00",
      "url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-87ph-jqwm-pg6r"
    }
  }
}

published 2026-10-06 12:32Z
last change 2026-10-21 12:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.