$ whoami
Developer Blog for Real-World Programming
$ git log --oneline --featured
$
$ cat ~/series
$ tail -f ~/articles
The November 2026 Next.js security release patches seven issues, and six live in the new Cache Components layer, the feature meant to make your app faster by remembering more. Three hit self-hosted next start specifically: the ones Vercel's own platform quietly absorbs.
Around 27 October, Claude Code started refusing to recreate existing games. No version bump, no changelog, no announcement: the text came from Anthropic's servers through a flag whose reader had shipped weeks earlier. I pulled three versions off npm and read the strings out of the binaries.
In 2019 Max Justicz showed apt would install a package an attacker swapped in over a redirect. In November 2026 he did it again, CVE-2026-109518, through a different door that ends in the same place: code as root from a man in the middle. The fix shows how apt reuses files on disk.
SudoSecurity runs on a $10 OVH box. That exact plan still costs $10. You just can't buy one. Nine months after the RAMpocalypse the problem changed shape: Hetzner's API returns 'no capacity' as its own error, resizing reprices you at today's rates, and the cheap tier has no stock left.
CVE-2026-123158 lets an attacker log into a locked account on musl-based systems like Alpine by sending a password nobody set. The trigger is one number, 257, and the reason is a C library returning a single asterisk. I reproduced the exact boundary against musl 1.2.4 and read the fix.
Composer 2.11 shipped a cooldown that refuses to install a version until it has aged. vlt now holds npm publishes until their dependencies actually exist, because 22% of new npm versions land broken. And Ruby Central's reviewers threw out 90% of what an AI scanner flagged.
Volexity caught an attacker chaining zero-days into unauthenticated root on an Ivanti Connect Secure appliance running the latest build. The payload never touched disk, commands rode in over the same HTTPS requests as the exploit, and Ivanti's Integrity Checker reported no modifications.
Gitea 28.3.0 landed November 1 with twenty-one CVE fixes. Read the list and a pattern jumps out: more than half are the same failure repeated across different route handlers, where a token scoped to public data gets handed private data anyway. That's not twenty-one mistakes.
CVE-2026-98432 is a use-after-free in the IPv4 TCP handshake, reachable by anybody who can reach a listening port, sitting in the kernel since 4.4. Red Hat scored it 5.9 moderate and deferred the fix. Then 8.1. Then 9.8.
Node.js 26 hit Long Term Support on October 28 as Lithium, supported through April 2029. Temporal ships enabled with no flag, which is the biggest thing to happen to JavaScript dates since Date was a mistake.
Running a proxy means turning authentication off on every server behind it. BungeeCord's own documentation admits what that costs you, and Velocity's docs are blunt that forwarding is not a substitute for a firewall. Here's the attack, and the exact config that closes it.
PostgreSQL slipped its release for the first time in years, and a core committer's explanation is four words long: LLMs happened. Back-patched commits are up over 60% on the stable branches while master commits went slightly down. Three major features got yanked between August 27 and September 15.
$ ls ~/sections
