The Control Plane — Week of Mon Nov 2, 2026
DigiCert moves to G5 roots on Nov 12, Chrome sets an emSign G1 cutoff, WordPress and GitLab bugs hit KEV, and Google explains its London outage.
Control Plane Labs Staff
Published November 5, 2026
This week’s theme is the backup you assume is there. Google’s London zone had two power feeds and a generator plant, and on October 20 it had neither: one feed was open for repairs and the generators never got a start signal. In PKI, the same assumption hides in trust stores. Most clients will follow DigiCert’s move to new roots without noticing, but the ones with pinned or hand-built trust stores won’t, and from November 12 that matters for every DigiCert, GeoTrust, Thawte, and RapidSSL renewal.
Kubernetes and cloud
There were no Kubernetes releases this week. The current patch lines are still 1.37.2, 1.36.6, and 1.35.10 from October 28. The patch release schedule puts the cherry-pick deadline for the November round on November 6, with releases targeted for November 10. After two rounds that slipped in October, plan maintenance windows for the week after that date rather than the day itself.
KubeCon + CloudNativeCon North America runs November 9 to 12 in Salt Lake City, according to the Kubernetes blog and the event page. Kubernetes on Edge Day returns as a co-located event on November 9, which the CNCF announced in October. Expect a burst of project releases and roadmap posts that week. Read the deprecation notes in them before you read the feature lists.
The cloud story of the week is a postmortem. On November 4, Google posted the root cause of the October 20 power loss in its London europe-west2-b zone, which The Register summarized the next day. The facility uses a 2N utility design with two feeders, A and B. Feeder B’s breaker had been opened for repairs after problems in a quarterly generator load test on October 14. On October 20, an external underground cable feeding A failed. The UPS systems carried the load for their designed five minutes, but a voltage-sensing design flaw and a PLC misconfiguration meant the generator plant never received a start command. The PLC logic reported a healthy utility source even though both distribution feeds were dead.
The outage took down Google Cloud services in the zone, including GKE workloads. The Register lists interruptions at Lloyds, HSBC, Royal Mail, and Revolut, and CDE News covered Revolut’s statement that customer money was safe. Google says it reprogrammed the PLC, tested changes to the zone’s electrical setup, and committed to faster automated customer communication for location-wide incidents.
The useful lesson for operators is the order of events. The redundancy was spent six days before the outage, during maintenance, and nothing outside the building reflected that. Your own systems have the same risk: a replica down for an upgrade, a second region drained for a migration, a standby node cordoned and forgotten. If your runbooks track “reduced redundancy” as a state with an owner and an end date, you will at least know when one more failure becomes an outage.
TLS and certificates
DigiCert switches default issuance to its G5 roots on November 12, between 18:00 and 20:00 UTC. Its root strategy notice says the change covers public DV, OV, and EV certificates across the DigiCert, GeoTrust, Thawte, RapidSSL, and Encryption Everywhere brands. The date was postponed from October 15. New certificates will chain to DigiCert TLS RSA4096 Root G5 or DigiCert TLS ECC P384 Root G5 instead of Global Root G2 or G3.
The reason is Chrome’s two-root limit. From September 15, 2027, the Chrome Root Store will support only those two G5 hierarchies for DigiCert. Customers with “mission-critical dependencies” on G2 or G3 can ask DigiCert to keep issuing from the old hierarchy during the transition, but the notice doesn’t give an end date for that option, and the Chrome deadline sets one in practice.
For most sites, nothing breaks. DigiCert says no action is needed if you serve the full chain, including the issuing intermediate. The exceptions are the usual ones. Managed trust stores (Java keystores, appliance bundles, internal proxies, and IoT firmware) need the G5 roots added before your first G5 certificate reaches them. Any configuration that pins a DigiCert root or intermediate needs to stop doing so. Check the clients that call your APIs as well as your browsers.
The same notice repeats a second deadline. On March 1, 2027, DigiCert removes the clientAuth extended key usage from public TLS certificates on all four roots. Chrome’s policy requires serverAuth-only subscriber certificates issued from March 15, 2027, and WorkOS has a good explainer of why mTLS setups that use public certificates as client identities need a private CA. Let’s Encrypt already stopped including clientAuth in February and retired its tlsclient profile in July.
Chrome also closed out the eMudhra incident from two weeks ago. A November 4 update to Google’s eMudhra post says that TLS certificates validating to emSign Root CA - G1 whose earliest SCT is after November 16, 2026, 23:59:59 UTC will not be trusted by default in Chrome 153 and later. Certificates logged on or before that time are unaffected. This is a different root from emSign ECC Root CA - G3, which Chrome removed on October 27. If you use emSign today, any renewal after November 16 should come from another CA in the Chrome Root Store.
Let’s Encrypt’s move to seven validation requests reaches production on November 10, per its community announcement. It’s the same day as the Kubernetes patches, so don’t plan certificate and cluster changes for the same window if you can avoid it.
Security
WordPress core is in the catalog. CISA added CVE-2026-119977 on November 3, with a federal deadline of November 6. It’s a time-of-check to time-of-use race in full-package core upgrades, rated CVSS 8.1, and it affects WordPress 4.7 through 7.1.3. BleepingComputer reports it’s being used for code execution. WordPress 7.1.4 shipped the fix on October 28 along with fixes for 21 other vulnerabilities, and backports went to 7.0.8, 6.9.11, and branches back to 4.7.39. WordPress 4.6 and older get no fix. Sites with auto-updates on are probably patched. Check the ones you pinned, the ones on managed hosts that hold minor versions, and any old installs no one owns.
GitLab’s CVSS 10 bug is the other urgent one. CVE-2026-97229 is an integer overflow in the regular expression compiler that GitLab CI/CD uses through Onigmo. GitLab fixed it on October 12 in 19.4.2, 19.3.5, and 19.2.8, and CISA added it to the KEV catalog on October 29. BleepingComputer reports that Shadowserver tracks more than 1,000 unpatched instances, and more than 11,300 exposed to the related CVE-2026-110264. The NVD entry has the affected ranges, and Alpine Linux published an incident note about the bug. Because the bug is in shared regex code, Ruby also shipped fixes in 3.3.13, 3.4.12, and 4.0.9 on October 23. See the Ruby news page. Self-hosted GitLab instances should be on a fixed release, and Ruby apps that compile user-supplied patterns should update too.
The rest of the week’s catalog additions are appliance and endpoint bugs. Ivanti Connect Secure CVE-2026-111357 and CVE-2026-118527 were added on October 30 and can be chained with CVE-2026-104935. Cisco ASA and FTD denial-of-service bug CVE-2026-76418 was added on October 29. CISA added Apple CVE-2024-27834 on November 4, a sign that old WebKit bugs still pay off for attackers on unmanaged devices.
GitBook also had a security incident. Its status page says it detected unauthorized access to parts of its infrastructure on November 2, contained it, and took services offline as a precaution, which took published documentation sites and the editor down on November 3. GitBook declared it resolved on November 4 and emailed customers about any actions needed. If your docs live there, read that email and rotate any integration tokens it mentions.
Web development and tooling
It was a quiet week for runtimes. The Node.js release index shows 26.13.0 LTS from October 28 as the newest stable build, and the first 27.0.0 alpha appeared on October 29 for the April 2027 major. If you build Node.js tooling, now’s a good time to add the alpha to a non-blocking CI job.
For WordPress, look at the release cadence, not just the CVE. Version 7.1.4 shipped 22 fixes in one release, and the KEV entry came six days later. Teams that run WordPress next to their main app (a docs site, a marketing site, a status blog) often leave it out of their patch process. Put those sites in the same inventory as your production services, with an owner and an update policy, or move them to a host that handles core updates.
SRE and reliability
GitHub had a rough Tuesday and Wednesday. UptimeRobot’s log records four GitHub incidents on November 4, the longest about two hours and four minutes, starting at 09:49 UTC and affecting pull requests, Git operations, and Issues. Separate Actions incidents followed, and the GitHub status page shows a Git operations incident on November 3 starting at 20:57 UTC. Cloudflare had Workers and Pages build errors for nearly five hours on November 3, plus Durable Objects errors in Dallas. Elastic Cloud’s serverless APM intake over PrivateLink failed on November 4, according to UptimeRobot.
The pattern is the one we wrote about last week: the dependency that hurts is the one you didn’t know was in the path. A two-hour Git outage stops deploys only if your deploy pipeline clones from GitHub at deploy time. If you mirror the deploy artifact or keep a pull-through cache, it’s an inconvenience. Count how many of your release steps need github.com to be up, and decide which ones should have a fallback.
Chart of the week: which roots DigiCert domains chain to
A week before DigiCert’s default changes, we wanted to see how much of the web is about to move. On November 5 we pulled the most recent indexed certificate for 109 widely used SaaS, developer, retail, finance, and media domains from CertIndex. 102 returned issuer data, and 56 of those, more than half, were issued by DigiCert under one of its brands. The dataset is here.
| Issuing CA | Domains | Examples |
|---|---|---|
| DigiCert Global G2 TLS RSA SHA256 2020 CA1 | 33 | grafana.com, sentry.io, datadoghq.com, linkedin.com, shopify.com |
| DigiCert Global G3 TLS ECC SHA384 2020 CA1 | 10 | stripe.com, adobe.com, netflix.com, akamai.com, ibm.com |
| DigiCert EV RSA CA G2 | 8 | verisign.com, zscaler.com, chase.com, citi.com, nytimes.com |
| GeoTrust TLS RSA CA G1 | 3 | amd.com, samsung.com, costco.com |
| Thawte TLS RSA CA G1 | 1 | hetzner.com |
| DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1 | 1 | lenovo.com |
None of the 56 came from a G5 intermediate, which is what you’d expect before November 12. The more useful number is the expiry dates. Of the 50 DigiCert certificates still valid at pull time, the latest expires on April 2, 2027 (grafana.com). So every domain here renews at least once after the switch and well before Chrome’s September 2027 cutoff. Unless the owner asks DigiCert to stay on G2 or G3, that renewal will chain to a G5 root. By spring 2027, this table should look completely different, and we plan to rerun it then.
The renewals start soon. instagram.com, whatsapp.com, and facebook.com expire on November 9, and nytimes.com on November 10, all just before the switch. stripe.com and americanexpress.com expire on November 12, the day of the switch, so they’ll likely renew on the old hierarchy. Most of the rest renew between December and March. 23 of the 56 still hold certificates longer than 300 days, issued before the 200-day cap, which is another reason their next renewal will look different.
Two caveats. Six DigiCert records had already expired at pull time, which means the replacement wasn’t indexed yet. We kept them because the issuer reflects what the domain was using. Seven domains returned no issuer data and were left out. We read the hierarchy from the issuing CA’s name, which marks G2, G3, and G5 hierarchies in DigiCert’s current naming, but we didn’t verify each chain to the root.
From the workshop
Two new pieces since the last recap. Kubernetes startupProbe vs readinessProbe explains what each probe gates, why slow-starting apps need a startup probe instead of a long initial delay, and how to tune thresholds without hiding real failures. Finding Every PHP and Node.js Runtime You Run covers how to find the runtime versions your servers actually load after PHP2Shell and Node2Shell, including containers and bundled binaries the package manager doesn’t see.
Recommended reading
- Read DigiCert’s root strategy notice and list every trust store you manage that lacks the G5 roots.
- Check your WordPress sites against the 7.1.4 release notes and your GitLab version against GitLab’s patch release.
- Read The Register’s account of Google’s London outage and ask where your own redundancy is quietly reduced right now.
Frequently asked questions
When does DigiCert switch to the G5 roots?+
Do I need to do anything for DigiCert's G5 change?+
What is changing for emSign Root CA - G1 in Chrome?+
Which WordPress versions fix CVE-2026-119977?+
Which GitLab versions fix CVE-2026-97229?+
What caused Google Cloud's europe-west2-b outage on October 20?+
When is the next Kubernetes patch release?+
Tags: #weekly-recap, #tls, #pki, #digicert, #wordpress, #gitlab, #kev, #sre