Go: Security Patches and Serialization Cleanup

Today's Go activity centers on security fixes across three packages plus efficiency improvements to JSON version two marshaling, alongside early groundwork for ARM64 SVE vector support.

Duration: PT2M44S

Episode overview

This episode is a short developer briefing from Go.

It explains recent repository work in plain language.

  • Show: Go
  • Published: 2026-08-14T13:07:01Z
  • Audio duration: PT2M44S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

This is Go, your daily developer briefing for August 14, 2026.

The top story today is security. Three separate fixes landed that close real vulnerabilities. The module system's checksum database got patched against a tile hash authentication bypass and a related lookup issue, addressing two CVEs at once through an updated x-slash-mod dependency. Separately, encoding a-s-n-one…

The second theme is JSON handling. Philip Pearl's pull request, number 80879, fixes an allocation problem in encoding JSON version two: when a struct field has an "is zero" method, the marshaler was calling reflect Interface in a way that allocated memory unnecessarily for non-pointer types. Swapping the order of…

Third, there's early platform work: Junyang Shao landed the initial ARM64 SVE vector extension support, both in the compiler's SIMD infrastructure and in the runtime's preemption handling. This is described as a minimal viable product — basic types, operations, and a simple test — reusing much of the existing AMD64…

A few smaller fixes round things out: a corrected pseudo-version string that was breaking "go doc dash http" for pkgsite, a new compiler error when both dash I and dash importcfg flags…

What…

Nearby episodes from Go

  1. Squeezing Stop-The-World Pauses Out of Crypto and Concurrency
  2. Weekly Recap - Correctness Fixes and Performance Tuning Under the Hood
  3. Precision Tuning in the Runtime
  4. Correctness Fixes in Math, JSON, and Runtime Sampling
  5. Compiler Squeezes Out Instructions, Tooling Speeds Up
  6. Trimming the Fat—Compiler and Crypto Cleanup
  7. Squeezing Cycles from the Compiler and Runtime
  8. Trimming the Fat in Hot Paths