Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence — Tuesday

October 13, 2026

🔥 What Changed

Normal Tuesday. Auth×mesh week continues: Envoy’s OAuth2 filter null-derefs on unauthenticated CONNECT (GHSA-8vc2-jrm4-835w) for a permanent edge DoS, distinct from yesterday’s X41 /dev/shm write-up. NATS Server v2.15.1 lands metalayer + filestore correctness after the 2.15.0 feature KEEP.

Holds: Azure PIR finals 7Q30-010 / 7QL5-Z50 still Mitigated/preliminary only (expect ~10-14/15). Go #82026 CL 846325 still NEW unmerged; #81957 Pratt CL 847406 NEW unmerged (updated 10-12); #81759 open CL 840845; #81864 fixed on tip (CL 841405 merged 10-07), no backport yet. grpc-go v1.85 still not released (milestone due 10-13; latest tag v1.84.0).

Envoy OAuth2 filter — unauth CONNECT null-deref crash (DoS)

GHSA-8vc2-jrm4-835w published 2026-10-06. envoy.filters.http.oauth2 dereferences :path without a null check; ASSERT compiled out of release. Classic CONNECT has no :path; Envoy permits that. One unauth CONNECT → SIGSEGV of the whole process; replay = permanent edge DoS. Ordinary prefix routes (no connect_matcher) are the vulnerable case — omitting upgrade_configs does NOT mitigate. Affected ≥1.16.0 <1.40.0. Patched: 1.36.12 / 1.37.8 / 1.38.6 / 1.39.3. Mitigation: RBAC deny :method: CONNECT ahead of OAuth2 filter. Distinct from yesterday’s X41 /dev/shm lateral-movement write-up.

Why you care: Auth/IAM rising; same Auth×mesh week as Envoy X41. Edge OAuth2 Envoy on the public internet is exactly the exposed posture.
Read Envoy GHSA-8vc2-jrm4-835w →

NATS Server v2.15.1 — metalayer + filestore correctness

Published 2026-10-09. Maintenance after 2.15.0: Go 1.27.2; consistent max_ha_assets enforcement on place/scale/move; filestore compaction race that could skip messages or lose redelivery; migration/R1 scale-up that could delete a running store or lose writes; leafnode pending-byte stall; many JetStream/MQTT/auth fixes.

Why you care: Board NATS 4. Material correctness after the 2.15.0 metalayer feature KEEP (09-28), not a fluff point release.
Read nats-server v2.15.1 →

📚 Worth Your Time

net/http: HTTP/2 client retries with a Request.Body it already closed — golang/go#82177

Filed 2026-10-13. Open. After errClientConnUnusable (SETTINGS MaxConcurrentStreams race, or slots held in pendingResets after deadline cancel), cleanupWriteRequest closes the body; shouldRetryRequest reuses that closed body → io.ErrClosedPipe. Repro on go1.27.2 + tip; hit in connect-go tests. Workaround: HTTP2Config.StrictMaxConcurrentRequests. Distinct from closed #82143.

Why you care: Board Go 60. Teaches HTTP/2 retry/body ownership; Connect/gRPC-over-HTTP2 clients without GetBody are in the blast radius.
Read on golang/go#82177 →

Cloudflare Logpush Transformers — in-process DataFusion (Go↔Rust Arrow IPC)

Published 2026-10-12. SQL filter/redact/reshape in the Logpush hot path inside Bufstream (~110M records/s). Worker prototype rejected (network hop). Go builds Arrow RecordBatch → Rust DataFusion via Arrow IPC/cgo; fail-closed (no raw fallback on transform failure; progressive delay then disable job). Complementary to yesterday’s Datadog Distributed DataFusion KEEP — embed vs distribute.

Why you care: Board DistSys 48. Concrete cross-language batch boundary + fail-closed delivery semantics.
Read on Cloudflare Blog →