Patch Week: Git Clones, 52 Postgres CVEs, Node 27 Certificates and Smarter Coding Agents
Git, PostgreSQL and Node.js all shipped releases web developers should care about this week, and Chrome wants to teach your coding agent the modern web.
Jason
5 min read·
Some weeks in tech are all launch events and big keynote promises. This wasn't one of them. Mid-November 2026 was a patch week. Git, PostgreSQL and Node.js all shipped things that matter if you write and deploy web apps, and Chrome quietly made its pitch for how coding agents should learn the web platform.
None of it is flashy, but most of it lands in your terminal, your database or your CI pipeline, so here's my read on what happened and what I think is worth doing about it.
Git 2.56.1: cloning a repo is no longer a harmless act
On November 10 the Git project released Git 2.56.1 with fixes for six vulnerabilities, along with backports to older maintenance branches. Git for Windows 2.56.1 followed a day later with the same fixes.
The headline bug is the uncomfortable one. A malicious repository can trigger code execution during a recursive clone, the kind you get with --recurse-submodules. The other five cover things like reference-name validation over protocol v2, binary patches, git fast-import and heap corruption during large merges. One of them mainly matters to hosting services that run merges for their users.
What makes this one worth more than a shrug is where clones happen now. It's not just you at your desk. CI runners clone constantly, often with credentials that can push code or read secrets. More and more, AI coding agents clone repositories on their own too. A bug that turns "clone this repo" into "run this code" hits all of those places at once.
The fix is boring, which is good news:
# Check what you're running (and do the same inside your CI images)
git --version
# If you must look at an untrusted repo before you can patch,
# clone it without submodules and read .gitmodules first
git clone --no-recurse-submodules https://example.com/some/repo.git
cat repo/.gitmodules
The part people forget is that Git often isn't installed just once. Docker base images, CI runner images, desktop Git clients and some IDEs bundle their own copy. Updating your laptop doesn't update the node:22-based image your pipeline built six months ago. If your builds use a pinned image, rebuild it. In GitHub Actions, actions/checkout doesn't fetch submodules unless you set submodules, so leave that off for code you don't control.
PostgreSQL's November release: a big batch of fixes, and goodbye to 14
On November 12 the PostgreSQL project shipped 18.7, 17.12, 16.16, 15.20 and 14.25, plus a second release candidate for PostgreSQL 19. Security coverage puts the number of CVEs fixed in this batch at 52, and a lot of them are rated high severity. A few, like an integer wraparound in the generation memory context that affects 16 through 18, are described as reaching arbitrary code execution.
Two practical points stand out to me.
First, these are minor releases. Postgres minors don't change the on-disk format, so upgrading is basically "replace the binaries and restart." There's no dump-and-restore and no migration. If you run Postgres yourself, this is about as cheap as security work gets. If you're on a managed service, check when your provider rolls the new minor out, and whether you have to click a button for it.
Second, PostgreSQL 14 has reached end of life, and 14.25 is its final release. Plenty of side projects and older production apps still sit on 14 because "it works." It will keep working, but it won't get any more fixes. Given how many CVEs this year touched 14, I wouldn't leave anything internet-facing on it.
If you aren't sure what your app is actually connected to (staging and production drift more than anyone admits), ask the database. With Prisma, it's one line:
// scripts/check-postgres-version.ts
import { PrismaClient } from '@prisma/client';
const prisma = new PrismaClient();
const [{ server_version }] = await prisma.$queryRaw<{ server_version: string }[]>`
SELECT current_setting('server_version') AS server_version
`;
console.log(`Connected to PostgreSQL ${server_version}`);
await prisma.$disconnect();
Running this against every environment takes a minute and usually turns up at least one surprise.
Node.js 27 alpha: certificates without OpenSSL gymnastics
The Node.js project is now publishing alpha builds for Node 27, and the alpha from November 12 includes a feature I've wanted for a long time: X.509 certificate generation with CSR support in node:crypto. Filip Skokan's pull request adds generateX509Certificate() and a synchronous generateX509CertificateSync(). They can create self-signed or issuer-signed v3 certificates, take subject and public key from a PKCS#10 request, and set typed options for extensions like Subject Alternative Name, Key Usage and Basic Constraints.
Today, if a test suite needs a throwaway TLS certificate, or a local dev tool needs to mint its own CA, you either shell out to openssl or pull in a third-party package. Having this built in is a nice quality-of-life win, especially for mTLS testing and internal tooling.
Two caveats. It's an alpha, so the API can still change before Node 27 goes stable, and I wouldn't build on it yet. The PR is also clear that it adds no extensions implicitly and that trust and CA authorization are your responsibility. That's the right call for a low-level crypto API, but it means you have to know what a correct certificate looks like.
Chrome wants your coding agent to read the docs
The most interesting AI-in-development news this week didn't come from a model launch. Google marked Modern Web Guidance 1.0 as stable. It's a set of guides for coding agents that bundles web platform best practices and browser-compatibility data, so an agent reaches for the modern native feature instead of whatever was popular in its training data.
# Installs the guidance into the current project for your coding agent
npx modern-web-guidance@latest install
Google suggests pairing it with Chrome DevTools for agents, which lets an agent run the code it just wrote in a real browser and inspect the result. The November DevTools update keeps building on that, with CSS style inspection for agents and an interactive editor for CSS anchor positioning.
My take: the biggest weakness of AI-generated frontend code isn't that it fails to run. It's that it's often dated, with JavaScript where CSS would do and a library where the platform has had a native API for two years. Giving agents curated, current guidance goes after exactly that. It doesn't replace knowing the platform yourself, though. "Modern" still doesn't mean "supported in every browser your users have," and you're the one who knows your audience.
Also worth knowing
- Google's November 2026 core update started rolling out on November 10. If your portfolio or product site sees ranking swings over the next couple of weeks, that's the likely cause. Wait for the rollout to finish before rewriting pages in a panic.
- Conference season continues: React Summit US and NG Poland are both running this month, so expect a wave of talk recordings on React and Angular to land soon.
What I'd actually do this week
If I had to boil this down to an hour of work, it would be this:
- Update Git on your machine, then rebuild any CI or Docker images that bundle Git.
- Check which Postgres version each environment runs, apply the latest minor release and put a date on getting off 14.
- Try Modern Web Guidance on a small frontend task and compare the output with what your agent produced without it.
- Bookmark the Node 27 X.509 API, but don't ship anything on it until it's stable.
Key takeaways
- Git 2.56.1 fixes six vulnerabilities, including code execution during recursive clones. Patch everywhere Git runs, not just on your laptop.
- PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix dozens of CVEs, and PostgreSQL 14 is now end of life.
- Node.js 27 alphas add built-in X.509 certificate and CSR support. It's useful, but still experimental.
- Modern Web Guidance 1.0 gives coding agents current web platform knowledge. It's a good guardrail, but no substitute for your own judgment.
Written by Jason
Published November 13, 2026 · Updated Nov 15, 2026