Digest #234: Doom in SQL, GitLab pushes by email, Linux kernel escapes and Postgres OOM tests

Also inside: GitHub Actions runners on Lambda microVMs, OpenAI's forum-to-repo exploit chain, and rebalancing EKS Pods across availability zones.

A leaked GitLab issue-by-email address can let someone push code and run CI jobs with its owner’s permissions, even from outside an IP allowlist. This week, you’ll turn Postgres memory management into an interactive explainer and debug a Kubernetes rollout that stalls while the old Pods keep serving traffic. You’ll also see how CedarDB got Doom’s game logic and renderer running in SQL, with multiplayer included.

If you’re interested in sponsoring this newsletter, reach out via LinkedIn or reply to this email.

My take: ask your AI for an explanation you can interact with

Newsworthy stories

• How a leaked GitLab issue-by-email address can push code and bypass IP restrictions

• Why containers are no longer a security boundary

• How an image upload and an SSO flaw opened a path to OpenAI’s internal repositories

• Can your managed Postgres survive a query that exhausts memory?

• Inside vibe-coded credential-harvesting dashboards and live Amazon Bedrock abuse

Tutorials of the week

• Write AWS DevOps Agent Skills from your operational runbooks

• Handle hot shards and isolate large tenants in sharded Postgres

• Run GitHub Actions runners inside Lambda microVMs

• Build on ECS primitives instead of convenience layers

• Run Doom’s game logic and renderer in SQL

• Debug a stuck Kubernetes rollout with a hands-on lab

• Fix EKS pod distribution drift with the Kubernetes descheduler

Videos of the week

Projects of the week

Meme of the week

Want to sponsor the newsletter? Book a slot - Q4 dates are open.