Read 2026-11-03
envoyproxy/gateway: technical due diligence, read from its repository
What Borehole read in envoyproxy/gateway's code and history at c1d70cc: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:3: names OpenSSF
Architecture & Codebase — including AI provenance
strongsite/static/js/hugo-benchmark-dashboard.js is 4,924 lines, 37× this codebase's median file
adequateThe median source file here is 132 lines. 17 files exceed 1,320 lines, the largest being 4,924. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
site/static/js/hugo-benchmark-dashboard.js:1 — 4,924 lines (37× median) |
internal/ir/xds.go:1 — 4,642 lines (35× median) |
internal/provider/kubernetes/controller.go:1 — 3,817 lines (28× median) |
internal/gatewayapi/route.go:1 — 3,787 lines (28× median) |
internal/gatewayapi/securitypolicy.go:1 — 3,669 lines (27× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong6 files still carry code deprecated more than two years ago
adequate6 files were marked deprecated over two years ago and still are, the oldest since Apr 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
proto/extension/context.pb.go — deprecated since Apr 2023 |
proto/extension/service.pb.go — deprecated since Apr 2023 |
api/v1alpha1/envoyproxy_metric_types.go — deprecated since Apr 2024 |
api/v1alpha1/envoygateway_types.go — deprecated since May 2024 |
api/v1alpha1/policy_helpers.go — deprecated since Jun 2024 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.9.3, is not on the branch this survey read; the newest release on it is v0.2.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.9.3 |
Security & Reliability Posture
adequate24 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: JWT, where fakes are usual |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
site/Dockerfile — runs as root |
2 outbound calls can wait forever
adequate2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
internal/cmd/envoy/shutdown_manager.go:217 — outbound call without a timeout |
internal/cmd/envoy/shutdown_manager.go:250 — outbound call without a timeout |
19 advisories against this project in the last 24 months, 8 high or critical
adequateThe newest was published on 2026-09-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 17 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.2.0. Answer lives in: the release you run, set against each fixed version. GHSA-mf24-chxh-hmvj (moderate), GHSA-j777-63hf-hx76 (high) are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: its keyword search for 'gateway' is too broad to read whole (2,772 records); NVD: 1183 records name gateway with nothing tying them to this repository (CVE-1999-1436, CVE-1999-1515, CVE-1999-1516, …).
| 2026-09-29: GHSA-gmx8-fhfh-mgjx (critical), fixed in 1.8.5: Privilege escalation from namespace admin to cluster-wide Secret reader via EnvoyProxy CR |
| 2026-09-29: GHSA-2fvr-33wm-m245 (moderate), fixed in 1.8.5: Envoy Gateway Panic in GatewayNamespaceMode |
| 2026-09-29: GHSA-qhrx-cqpw-vr6p (high), fixed in 1.8.5: EnvoyProxy strategic-merge patch applied to Deployment without field allowlist |
| 2026-09-03: GHSA-gh7q-fc5g-jqj5 (high), fixed in 1.8.4: SecurityPolicy targeting unprogrammed TCP listener enables cross-tenant control-plane denial-of-service |
| 2026-09-03: GHSA-pvjw-x88g-5xqw (moderate), fixed in 1.8.4: HTTPRouteFilter credential injector nil dereference enables cross-tenant control-plane denial-of-service on shared Gateway |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on envoyproxy/gateway: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.