Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-53713

Vulnerability in github.com/envoyproxy/gateway (CVE-2026-53713)

Summary

vulnerability in github.com/envoyproxy/gateway (CVE-2026-53713). Risk of unauthorized operations or information disclosure. Exploitable via ``to_absolute_normalized_path``. Mitigation: upgrade to `1.7.4` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-53713** has been found in github.com/envoyproxy/gateway. Attackers can target a specific entry point like ``to_absolute_normalized_path`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade github.com/envoyproxy/gateway to **1.7.4** or later. If unsure, ask your IT team or search "github.com/envoyproxy/gateway CVE-2026-53713" on the vendor's site.
CVE-2026-53713 (github.com/envoyproxy/gateway) — CWE-20 / Attack surface: `to_absolute_normalized_path` / `is_critical_path` / `EnvoyExtensionPolicy` / `Warning` Patched: `1.7.4` — apply immediately Workaround: Please refer to the `Warning` section in [Lua docs](https://gateway.envoyproxy.io/v1.8/tasks/extensibility/lua/) for measures to reduce risk. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-20) exists in github.com/envoyproxy/gateway. Attackers reach the vulnerable code path via ``to_absolute_normalized_path`` without authentication.
📍 Affected scope
github.com/envoyproxy/gateway — . Attack surface: `to_absolute_normalized_path` / `is_critical_path` / `EnvoyExtensionPolicy` / `Warning`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.4**.
🛡️ Workaround
Workaround: Please refer to the `Warning` section in [Lua docs](https://gateway.envoyproxy.io/v1.8/tasks/extensibility/lua/) for measures to reduce risk.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/envoyproxy/gateway' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/envoyproxy/gateway' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/envoyproxy/gateway` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    Please refer to the `Warning` section in [Lua docs](https://gateway.envoyproxy.io/v1.8/tasks/extensibility/lua/) for measures to reduce risk.

    パッチが適用されるまでの応急処置として、Please refer to the `Warning` section in [Lua docs](https://gateway.envoyproxy.io/v1.8/tasks/extensibility/lua/) for measures to reduce risk. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade github.com/envoyproxy/gateway to 1.7.4

    ステージング環境で 1.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/envoyproxy/gateway
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.4"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →