I ran govulncheck on a quiet Saturday and it flagged GO-2026-5856, a reachable vulnerability in the crypto/tls package of Go 1.26.4. Bumping to 1.26.5 fixed it. While I had the hood open, I went looking for the next problem.

Parser output is trusted HTML

The templates render parsed content with templ.Raw, so the parser decides what reaches the page. Links now go through a check before they become <a href>:

  • relative paths, http, https, and mailto pass
  • protocol-relative URLs like //evil.example fail
  • any other scheme fails, javascript: included

A bad link fails the parse, and a failed parse stops the app at startup.

Bounding requests

LimitValue
search query256 bytes, then 400
raw query string512 bytes, then 400
request headers1 MiB, read within 5 seconds
writes30 seconds

I also fixed the gzip middleware. It used to flush an empty gzip stream on responses that should not have been compressed at all. And every response now carries HSTS and a Permissions-Policy that turns off the camera, microphone, and geolocation.

Pinning the build

  • Go 1.26.5 everywhere: go.mod, Dockerfile, CI
  • Tailwind binary checked against its official SHA-256
  • GitHub Actions pinned to commit SHAs
  • test workflow token cut down to read access
  • GoReleaser pinned to a major version

Every behavior change started as a failing test. I finished with go test -race, go vet, and a clean govulncheck run, all inside one afternoon.