Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence — Wednesday

November 11, 2026

šŸ”„ What Changed

A normal Wednesday with four items. Go 1.27.4 and 1.26.11 shipped at 22:44 IST last night with the 12 pre-announced security fixes. Eleven of them close cgo/linker flag-injection paths in cmd/go, cmd/cgo, cmd/compile and cmd/link, where building a malicious module could run code or write files at build or link time. The twelfth, CVE-2026-97054, is a runtime crash in the HTTP/1 server when MaxBytesReader is used. CVE-2026-97047 (#82948, the HTTP/2 trailer O(N²) DoS) did not ride along. It is still open with milestone Go1.28. Git 2.56.1 (plus backports down to 2.50.2) fixes six CVEs, including code execution during a recursive clone of a malicious repository. SpiceDB v1.57.1 fixes two ways expired relationships could still grant permissions. For Worth Your Time, the Go team's 17th-anniversary post doubles as a 1.28 roadmap.

Also seen: Go #82853 (HEAD-as-GET middleware response desync) closed as not planned on 11-11: neild cited the Handler contract ("handlers should not modify the provided Request"), so CL 858982 will not land. Go #82977/#82978: windows/amd64 exception recovery can write below a goroutine stack and corrupt the heap (AMX hosts, including GitHub windows-latest runners), with backport requests for 1.26/1.27. gopls still v0.24.0 (#82891 vscode-go follow-up CL 861497). Telepresence CVE-2026-102340: Traffic Manager gRPC had no auth, so any pod could claim a namespace and intercept services (GHSA-j8j4-rw65-56r6), plus a session-hijack CVE-2026-102339. Kubeflow Pipelines advisory batch (critical CVE-2026-77596 missing authz on shared uploads). Traefik v3.7.18 / v2.11.62 (BasicAuth length cap, dot-segment path normalization, Host matcher validation). OPA v1.22.3 bumps klauspost/compress for the zstd panic CVE-2026-116591. Airbnb open-sourced Skipper, an embedded JVM workflow engine (lease-based scheduler on the service's own DB, replay plus checkpoints). OpenSSL merged 5 low-severity fixes.

Holds: Go CVE-2026-97047 (#82948, milestone Go1.28, CL 862201; watch for a 1.27.5/1.26.12 or a fix in 1.28); Go #82945 TLSNextProto h2 regression (still untriaged); Go #82977/#82978 windows heap-corruption backports; upstream Keycloak fix for CVE-2026-120984 (latest upstream still 26.8.2); gopls release for #82821 + #82891 (still v0.24.0); CVE-2026-98432 OpenShift CoreOS; x/oauth2 CL 854305; Kafka 3.9.3 (code freeze 11-20); NATS 2.15.3/2.14.10 GA (still RC.2); Postgres 19 RC2 ~11-12 / GA ~11-19.

Go 1.27.4 / 1.26.11 security release: 11 cgo/linker build-time code-execution CVEs plus a net/http MaxBytesReader HTTP/1 server crash; CVE-2026-97047 not included

Go 1.27.4 and 1.26.11 are out on go.dev/dl with the 12 CVEs pre-announced on 11-05. Runtime-facing (1): CVE-2026-97054 (#82563). When MaxBytesReader's limit is exceeded, the HTTP/1 server sets Connection: close without synchronization, so a handler that reads the request body concurrently with writing response headers can crash the whole server with a runtime panic. This affects servers using http.MaxBytesReader / MaxBytesHandler. Build-time (11), from building a malicious package that uses cgo or ships .syso files: CVE-2026-97033 (#82577) bans --sysroot/-target and restricts -x/-isysroot/-Wl,-syslibroot; 97034 (#82576) GCC spec files in -L/sysroot dirs via -fopenmp/-fsanitize=; 97035 (#82575) Clang -gen-* / GCC -gnat* slipping through the -g* wildcard; 97036 (#82574) Darwin -l to_library LTO-plugin loading; 97037 (#82573) linker-script injection via split -Wl, flags; 97038 (#82572) crafted .syso/linker inputs (implicit ld scripts, PE .drectve, Mach-O LC_LINKER_OPTION, LTO IR); 97039 (#82571) #cgo pkg-config: sanitization bypass; 97040 (#82570) .syso disguised as a Go object carrying cgo_ldflag; 97041 (#82569) commas in //go:cgo_* directives; 97042 (#82568) cgo_import_dynamic and PE DLL-name traversal on Windows; 97043 (#82567) escaped quotes in //go:cgo_ldflag. Most build-time issues came from a Go Security Team internal audit; 97040/97041 are credited to RyotaK (GMO Flatt Security). The release-notes line lists security fixes to cgo, the go command, the compiler, the linker and net/http, plus bug fixes in crypto/tls, crypto/rsa, crypto/hkdf, crypto/fips140 and net. CVE-2026-97047 (#82948, HTTP/2 trailer dedup DoS) is NOT in this release. It is still open, Security + release-blocker, milestone Go1.28, with CL 862201 in review.

Why you care: Go is your top-weighted skill. The build-time CVEs matter wherever CI builds third-party modules, including dependency bots, go install of untrusted tools, and multi-tenant build farms: before this release, a dependency's #cgo lines could run code on the build host. The MaxBytesReader crash is a remotely triggerable panic for any HTTP/1 service that caps body size, which is most JSON APIs. Action: bump toolchains, base images and toolchain lines in go.mod to 1.27.4 / 1.26.11, rebuild and redeploy, and keep tracking #82948 separately for ReverseProxy fronts.
Read Go security announcement → Also: go.dev → Also: go.dev → Also: github.com →

Git 2.56.1 (backports to 2.50.2): six CVEs, including code execution on recursive clone and path traversal via a server-advertised HEAD

The Git project released 2.56.1, with backports 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. CVE-2026-111760: an integer truncation in index handling lets an extremely long path pass validation under one name and be written under a shorter one, so a submodule's .git can be replaced with a symlink to attacker config or hooks, giving code execution during git clone --recursive. CVE-2026-113408: a malicious protocol-v2 server can advertise an unborn HEAD symref containing path traversal, and a later branch update writes outside the refs directory. CVE-2026-114467: a tag with more than two GPG signatures overflows a fixed stack array when merged. CVE-2026-105437: heap corruption from size overflow in large merges (for example, many conflicts plus a big conflict-marker-size). CVE-2026-114469: an out-of-bounds read from binary patches whose decompressed size bypasses the ~1 GiB check. CVE-2026-114466: fast-import stream features rewrite-submodules-from/to and export-pack-edges are now refused unless --allow-unsafe-features is set. GitHub says github.com and GHEC are already patched, GHES fixes are in 3.19.15 / 3.20.11 / 3.21.9 / 3.22.4, and Actions/Codespaces images are getting patched Git.

Why you care: Cloud/K8s Ɨ Security. CI runners, GitOps controllers (Argo CD, Flux), Go module fetches of VCS sources, and any service that merges or clones untrusted repos shell out to Git. Update base images and runner Git, not just laptops. Until then, avoid recursive clones and tag merges from untrusted sources.
Read GitHub Blog post →

SpiceDB v1.57.1: expired relationships could still grant permission, via a check-path optimization (GHSA-w278) and a cache TTL regression since v1.54.0 (MySQL indefinitely)

Two separate ways expired relationships could keep authorizing. GHSA-w278-32qg-48q5 (rated low, affects >=1.40.0, fixed 1.57.1): when a relation is a union of a type with expiration and the same type with a subject relation (e.g. user with expiration | user#manager), the check path miscounted user#manager as a non-expiring direct subject. It then skipped the expiration filter in the datastore query, so an expired relationship counted until garbage collection. Cache regression (#3431): since the v1.54.0 move to Otter, every cache read extended the entry's expiry by another TTL, so dispatch/relation cache entries that are read more often than the TTL never expired. On MySQL, where the revision only advances on writes, an expired relationship could keep granting permission indefinitely, even with fully_consistent, until the next write. The release also makes the CockroachDB GC window come from the relation_tuple table's zone config instead of RANGE default, and consistently rejects schemas that transitively include wildcard subjects.

Why you care: Auth/IAM Ɨ Distributed Systems, with SpiceDB on the board. This is the classic stale-cache-versus-revocation failure in a Zanzibar-style system: time-bound grants (break-glass access, trials, temporary sharing) silently outliving their expiry. If you run SpiceDB ≄1.54 with expiring relationships, especially on MySQL, upgrade.
Read SpiceDB v1.57.1 release → Also: github.com → Also: github.com →

šŸ“š Worth Your Time

Go Turns 17: the Go team's year in review doubles as a Go 1.28 roadmap (inferred composite-literal types, SIMD graduation, generic collections in x/exp, a proposal-process overhaul)

Austin Clements recaps Go 1.26 and 1.27: generic methods, encoding/json/v2 GA (v1 now implemented on top of v2), the goroutineleak profiler GA, HTTP/1 transport auto-draining small unread bodies (up to 5Ɨ for sequential requests), Green Tea GC by default, size-specialized allocation (small allocs up to 30% faster), post-quantum TLS defaults and crypto/mldsa, and the first URGENT-track release for the eMudhra incident. Looking ahead: Go 1.28 will let composite literals omit types that can be inferred; a batch of accepted generic-collection proposals (sets, ordered maps and more) lands in golang.org/x/exp "over the next few weeks"; a large subset of simd/simd/archsimd should graduate in 1.28, with arm64 SVE targeted for 1.29; reducing memory footprint is a major priority; 1.28 writes export data early to increase build parallelism; and there is longer-term work on cgo builds without a C toolchain. The team is also restructuring the proposal process and building a contributor ladder with non-Google maintainers.

Why you care: Go is your top skill. It is one authoritative page for what changed in the two releases you are learning on and what to expect in 1.28 (Feb 2027), useful both for interviews and for deciding what to adopt now (json/v2, goroutineleak) versus wait for (x/exp collections, simd).
Read Go Turns 17 →