On Call Brief – Week of October 25–31, 2026

2026-10-25 — 2026-10-31 Briefing: 2026-10-25 Published 2 weeks ago (Nov 1, 2026 3:46 am EST) 25 min read
Share
Category:
Tags:

This week's top stories

1. Brotli decoder RCE (CVE-2026-111497) is now exploited in the wild - patch Node.js, Envoy, Istio, .NET and every image that bundles libbrotli

  • Category: Security / Patch
  • What happened: CVE-2026-111497 is an out-of-bounds write in Google's Brotli decoder: an invalid block switch is reported as "need more input" instead of a format error, so the decoder keeps appending attacker-controlled bytes to an eight-byte internal buffer. Node.js disclosed it on Oct 21 (reachable through node:zlib; fixed in 22.23.4, 24.22.1 and 26.12.1, credited to OpenAI Codex Security). The same decoder is vendored almost everywhere: Envoy published GHSA-3wvj-j6qm-62mr (CVSS 9.2, Critical) on Oct 23 for deployments with the Brotli decompressor configured; Istio lists it under ISTIO-SECURITY-2026-007; Microsoft shipped out-of-band .NET 8.0.33, 9.0.22 and 10.0.14 (GHSA-p3jp-9v83-76w9, CVSS 8.1) on Oct 25-26 for ASP.NET Core request decompression with "br", HttpClient AutomaticDecompression that includes Brotli, and BrotliStream / BrotliDecoder; PHP rebuilt its Windows packages (8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1) with Brotli 1.2.1 on Oct 26. Help Net Security reports in-the-wild exploit traffic from Oct 26 and a CISA KEV listing on Oct 27, and that the fix sat in google/brotli's main branch since February without a release or advisory.
  • Why it matters: Anything that decompresses Brotli it did not produce is reachable by an unauthenticated remote attacker: a Node service that brotli-decompresses request bodies, an Envoy or Istio listener with the Brotli decompressor, an ASP.NET Core app with request decompression enabled, an HttpClient that auto-decompresses responses from servers you do not control. Because the decoder is statically bundled, a package-manager CVE scan of the base image will miss most copies.
  • Do this Monday: Node.js: 22.23.4, 24.22.1 or 26.12.1 (EOL lines stay vulnerable). Envoy: 1.40.0, 1.39.3, 1.38.6, 1.37.8 or 1.36.12; Istio: 1.31.2, 1.30.6 or 1.29.9. .NET: 8.0.33, 9.0.22 or 10.0.14 - until then remove the "br" provider from request decompression and take Brotli out of AutomaticDecompression (neither is on by default). Rebuild images that bundle libbrotli onto 1.2.1 (1.1.1 or 1.0.10 on the older lines) and Windows PHP onto the -1 packages. Inventory with `node --version`, `dotnet --list-runtimes` and `envoy --version` across your fleet rather than trusting the OS package list, and grep Envoy and Istio configs for the brotli decompressor before deciding who goes first.
  • Sources: Node.js October 2026 security releases, Microsoft advisory for .NET, Envoy advisory, ISTIO-SECURITY-2026-007, PHP Windows rebuild announcement, Help Net Security on exploitation and KEV
  • Tags:
  • Editor's note: Added by the editor. The feeds carried this only as a Lightning link and an Envoy release note; the KEV listing and the Envoy, Istio and .NET advisories this week make it the fix with the widest blast radius.

2. LiteLLM PyPI Package and Docker Images Compromised to Steal Cloud and AI Credentials LiteLLM 1.107.0 on PyPI

  • Category: Community
  • What happened: The LiteLLM 1.107.0 package on PyPI and its Docker images were compromised through a lookalike source, allowing malicious Python startup hooks to steal cloud and AI tool credentials. This compromise involves a remote Python loader controlled by a GitHub-hosted file.
  • Worth reading: Upgrade to LiteLLM version 1.108.0 or later and audit your systems for any unauthorized credential access.
  • Source: CloudSecList
  • Tags:

3. The Pulse: Firebase’s global outage & poor response

  • Category: Deep Dive
  • What happened: On Sept 28 a routine cleanup removed a remote-config flag that the Google Analytics for Firebase SDK on Apple platforms still referenced. The backend served the malformed payload for 2 hours 11 minutes (17:41-19:52 PDT) and every iOS app that fetched it crashed once, then fell back to cached config; Google says no device entered a crash loop. Its Oct 2 postmortem commits to a GA4F SDK patch with strict payload validation, an audit of the other Firebase SDKs for the same parsing weakness, and SDK outages on the status dashboard. The Pragmatic Engineer piece is about the response, which developers found slow and poorly communicated.
  • Why it matters: Review your dependency on Firebase and prepare for potential outages by implementing fallback mechanisms.
  • Sources: SRE Weekly, SRE Weekly
  • Tags:

4. Gheist: 13,500 planted ci-sync branches across 850+ GitHub accounts dumped Actions secrets - GitHub's run hold protects public repos, not private ones or GHES

  • Category: Deep Dive
  • What happened: Wiz Research (Oct 25) has tracked the campaign since Sept 15. A tool fed with stolen tokens (infostealer logs, earlier supply-chain leaks) pushes a branch named ci-sync- plus six random characters containing one file, .github/workflows/sync-check.yml ("ci: sync config"); the push-triggered job prints toJSON(secrets) base32-encoded, which GitHub's log masking does not catch, then the tool downloads the log through the API and deletes the run seconds later - there is no outbound connection to block. A self-hosted-runner variant mounts the host filesystem through the Docker socket. GitHub's July 28 hold on suspicious workflow runs stopped every public-repo run Wiz checked; in private repos and GitHub Enterprise Server the runs completed, and in some organizations attacker branches assumed AWS roles through OIDC.
  • Why it matters: Review access controls for GitHub tokens in private and Enterprise repositories to prevent unauthorized access.
  • Do this Monday: Search for branches matching ^ci-sync-[0-9a-z]{6}$, audit-log runs deleted within a minute of completing, and the "gheist" user agent; check cloud logs for OIDC role assumptions whose subject names a ci-sync- branch. On a hit, rotate every repository, organization and environment secret the repo could reach, revoke the tokens that pushed, check their owners' machines for infostealers, and treat any self-hosted runner that ran the branch (and its instance role) as compromised. Then scope OIDC trust policies to protected branches or environments and require reviewers on environments holding production secrets.
  • Sources: Wiz Research, DevOps.com
  • Tags:

5. AI coding agents hijacked using AGENTS.md file in Downloads folder

  • Category: Deep Dive
  • What happened: Researchers discovered that a malicious AGENTS markdown file placed in a user's Downloads folder can manipulate an AI coding agent to install a rogue npm package, posing a security risk.
  • Takeaway: Review and clean the Downloads folder for any unauthorized AGENTS.md files to prevent potential exploitation.
  • Source: Bleeping Computer
  • Tags:

6. Railway's preliminary report: at most 1.85% of workspaces had variables decrypted - reconnect GitHub, replace ghcr.io tokens, redeploy bucket services

  • Category: Deep Dive
  • What happened: Railway's Oct 22 preliminary report (updated Oct 26) puts the attack window at Oct 20 13:58 UTC to Oct 22 03:32 UTC: the attacker escalated privileges in build infrastructure, obtained CI credentials, queried encrypted environment variables and decrypted a subset, apparently hunting AI-provider API keys. At most 1.85% of workspaces had variables compromised, but Railway handed a larger set of keys to upstream providers for revocation, so more customers received reset notices. User accounts were not accessed; access to source code is not yet ruled out. Railway rolled every storage-bucket credential and every Railway GitHub App installation and revoked all Railway tokens, which is why GitHub deploys and ghcr.io pulls broke.
  • Why it matters: The outage impacted developers' ability to deploy applications, highlighting the importance of securing environment variables. Users should be aware of the need to rotate API tokens and monitor for any further updates from Railway regarding security measures.
  • Do this Monday: If you signed up before Oct 21, rotate the keys stored on Railway and re-apply sensitive variables. Reconnect your GitHub account and confirm the Railway GitHub App's repository access and each service's source and autodeploy setting; delete the old ghcr.io tokens on GitHub and enter new read:packages tokens per service; update services and CI jobs that reference old bucket keys and redeploy them, since containers read variables only at startup. Review GitHub, Docker Hub and Railway audit logs for variable reads, registry-credential changes and deployments in the window, and export the Railway audit log now (retention depends on plan). Redeploy the latest commit: pushes made during the pause were not deployed.
  • Sources: Railway preliminary report, Railway recovery steps, dev.to explainer, r/devops discussion
  • Tags:

7. Pods Running, Service returns 503: the selector bug that fools everyone

  • Category: Deep Dive
  • What happened: The article discusses a common issue in Kubernetes where a service returns a 503 error despite pods appearing healthy. It explains that the root cause often lies in the service's selector, which may not match the labels of the running pods, leading to an empty endpoint list. The author illustrates this with a practical example, showing how to diagnose the problem using kubectl commands and highlighting the importance of checking EndpointSlice objects. The piece emphasizes that even when pods are running, misconfigured selectors can prevent traffic from reaching them.
  • Takeaway: Understanding this selector issue is crucial for troubleshooting service availability in Kubernetes. Operators should ensure that service selectors correctly match pod labels to avoid 503 errors, even when pods appear healthy.
  • Source: dev.to (SRE tag)
  • Tags:

8. GCP: VPC Service Controls perimeters can now include folders, and ingress/egress rules accept folders, organizations and PSC endpoints

  • Category: Community
  • What happened: Google Cloud has enhanced VPC Service Controls by adding folder membership, allowing contained projects to inherit policies. The ingress and egress rules now support folders, organizations, and Private Service Connect endpoints.
  • Why it matters: Review and update your VPC Service Controls configurations to utilize folder membership for policy inheritance.
  • Sources: CloudSecList
  • Tags:

CVE & Security

9. CISA KEV adds GitLab's CVSS-10 CI regex RCE (CVE-2026-97229) and a Cisco ASA/FTD SSL VPN zero-day (CVE-2026-76418)

  • Category: Security / Patch
  • What happened: CISA added both on Oct 29. CVE-2026-97229 is an integer overflow in GitLab's CI/CD regular-expression compiler (Ruby's Onigmo engine) that gives OS command execution as the git user; GitLab patched it on Oct 12 in 19.4.2, 19.3.5 and 19.2.8. A second CVSS-10 regex overflow, CVE-2026-110264, followed on Oct 21 in 19.5.1, 19.4.3, 19.3.6 and 19.2.9 (backported to 19.1.9, 19.0.10 and 18.11.13), and GitLab's latest set (19.5.3, 19.4.5, 19.3.7, 19.2.10) also drops the eMudhra intermediates. GitLab.com and Dedicated are patched. The Cisco flaw is a NULL-pointer dereference in Secure Firewall ASA and FTD remote-access SSL VPN (CVSS 8.6): an unauthenticated attacker can make the device reload. Cisco published it on Oct 28 and says it is being exploited. Only devices with webvpn enabled on an interface and secondary-authentication-server-group configured on a tunnel group (including DefaultWEBVPNGroup) are affected.
  • Why it matters: Upgrade GitLab to the latest version to mitigate CVE-2026-97229, as it is actively exploited.
  • Do this Monday: Self-managed GitLab: upgrade to at least 19.5.1, 19.4.3, 19.3.6 or 19.2.9 (both CVSS-10 regex bugs), preferably 19.5.3, 19.4.5, 19.3.7 or 19.2.10; the releases carry migrations, so expect downtime on single-node instances. Until then keep untrusted users from pushing branches or creating public projects. ASA and FTD: look in the running config for webvpn with an enabled interface and for secondary-authentication-server-group under any tunnel group; first fixed releases are ASA 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48 and 9.24.1.27, FTD 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3 and 10.1.1. There is no workaround. Cisco's interim mitigation depends on DefaultWEBVPNGroup: if it does not use secondary authentication, `no tunnel-group-list enable` removes the connection-profile chooser without weakening authentication; if it does, the only mitigation is `no secondary-authentication-server-group` on that group, which Cisco says lowers the remote-access VPN security posture.
  • Sources: GitLab 19.4.2 / 19.3.5 / 19.2.8 (CVE-2026-97229), GitLab 19.5.1 / 19.4.3 / 19.3.6 / 19.2.9 (CVE-2026-110264), GitLab 19.5.3 / 19.4.5 / 19.3.7 / 19.2.10, Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75, The Hacker News
  • Tags:

10. VMware ESX audit-logging bypass CVE-2026-41709 (CVSS 2.7) was used as a zero-day - it has been patched since July's VMSA-2026-0006

  • Category: Security / Patch
  • What happened: CISA has added CVE-2026-41709, a vulnerability in Broadcom VMware ESX, to its Known Exploited Vulnerabilities catalog after it was exploited by the China-linked group Warp Panda in attacks against the U.S. legal sector. This zero-day flaw reduces audit trail visibility, potentially allowing attackers to cover their tracks during intrusions.
  • Why it matters: Upgrade VMware ESX to the latest version to mitigate CVE-2026-41709 and prevent exploitation.
  • Do this Monday: The logging fix alone is ESXi80U3j-25429389 (8.0), ESXi-9.0.2.0100-25595025 (9.0) or ESXi-9.1.0.0-25370933 (9.1), but the same advisory (VMSA-2026-0006, July 29, updated Aug 19) also fixes the VMXNET3 VM escape CVE-2026-47876 (9.3) and the vCenter authentication bypass CVE-2026-59309 (9.8), so take the builds that close everything: ESX 8.0 to ESXi80U3k-25595708 (or ESXi80U2f-25626445 on the 8.0 U2 line), 9.0 to ESXi-9.0.2.0100-25595025, 9.1 to ESXi-9.1.0.0200-25557999, VCF 5.x via the KB88287 async patch; vCenter to 8.0 U3k / U2f, 9.0.2.0100 or 9.1.0.0300. A host still missing this advisory has bigger problems than unrecorded admin actions; Broadcom lists no workarounds.
  • Sources: Broadcom VMSA-2026-0006, The Hacker News
  • Tags:

11. Attackers Exploit PHP2Shell Flaws in Internet-Exposed Palo Alto Networks Management Interfaces

  • Category: Security / Patch
  • What happened: Two critical PHP runtime vulnerabilities, CVE-2026-109618 and CVE-2026-109619 (both CVSS 9.2), enable unauthenticated remote code execution and are being actively exploited in the wild, with CISA adding them to the Known Exploited Vulnerabilities catalog after confirmed attacks on government entities and Palo Alto Networks management interfaces. These flaws exist in the PHP engine itself and cause memory corruption and use-after-free conditions, requiring operators to patch the underlying PHP runtime rather than application code. Operators should immediately upgrade to patched PHP versions on all systems, particularly those with internet-exposed management interfaces, and review access logs for unauthorized access attempts or unexpected command execution. The vulnerabilities have been exploited to exfiltrate sensitive data including password hashes, with evidence suggesting attackers are using AI platforms to accelerate exploitation techniques and global scanning for vulnerable targets.
  • Why it matters: Restrict access to Palo Alto Networks management interfaces from the internet until further notice.
  • Do this Monday: Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (released Oct 21; 8.2 reaches end of life Dec 31) or your distribution's backport. PHP 8.1 and older get no release from the project, only source patches for 7.4, 8.0 and 8.1. If you cannot patch today, set session.upload_progress.enabled=0 in php.ini or the FPM pool config (not ini_set or .user.ini) and restart every worker - PHP says this blocks the confirmed session paths but not every variant, and that memory_limit or post_max_size tweaks do not make an install safe. On Linux web hosts also confirm the May 2026 Fragnesia kernel fix (CVE-2026-46300, XFRM ESP-in-TCP, local root) is installed: it is reported as the privilege-escalation step chained after PHP2Shell.
  • Sources: PHP security advisory and releases (Oct 21), The Hacker News, The Hacker News on the government intrusion, Red Hat on CVE-2026-46300
  • Tags:

12. CVE-2026-98432: Linux TCP Use-After-Free Risk and Patch Validation

  • Category: Security / Patch
  • What happened: CVE-2026-98432 is a use-after-free vulnerability in the Linux kernel's IPv4 TCP handshake path that could allow remote code execution. The memory corruption issue affects the TCP implementation and requires immediate kernel updates across all Linux distributions. Operators running self-managed Linux instances must update their kernel packages to the latest patched version provided by their distribution and perform a full system reboot to apply the fix. AWS-managed services will receive automatic updates, but customers with EC2 instances or other self-managed Linux systems need to manually apply the kernel update and reboot to eliminate the exposure window.
  • Takeaway: Informational: a discussion on a Linux TCP vulnerability without immediate patch details.
  • Sources: Penligent Ai via Hacker News (incidents), AWS Security Bulletins
  • Discussion: https://news.ycombinator.com/item?id=50299182
  • Tags:

13. ALAS2KERNEL-5.15-2026-120 (important): kernel

  • Category: Security / Patch
  • What happened: A security advisory has been issued for Amazon Linux 2 regarding CVE-2026-98432, which affects the kernel. This advisory indicates that there is an important security vulnerability that needs to be addressed.
  • Do this Monday: Upgrade Amazon Linux 2 to mitigate CVE-2026-98432.
  • Source: Amazon Linux 2 Security Advisories (ALAS2)
  • Tags:

14. Brotli2Shell: Frequently asked questions for Google Brotli decoder vulnerability (CVE-2026-111497)

  • Category: Security / Patch
  • What happened: CVE-2026-111497 is a buffer overflow vulnerability in Google's Brotli decoder library that allows remote code execution through an out-of-bounds write, with public proof-of-concept exploits now available. The flaw affects multiple platforms including Node.js, .NET, Bun, Envoy Proxy, and Istio, where an unauthenticated attacker can achieve privilege escalation or arbitrary code execution by sending specially crafted Brotli-compressed data over the network. Operators should immediately update affected components to patched versions: check vendor security advisories for your specific runtime or proxy implementation as each project distributes fixes independently. For Node.js deployments, upgrade to the latest LTS releases; for .NET applications, apply the latest security updates through standard update channels; for Envoy and Istio users, upgrade to the latest patch releases that incorporate the fixed Brotli library version.
  • Do this Monday: Upgrade any affected software using the Brotli decoder to mitigate the risk of remote code execution.
  • Sources: Security Boulevard, Microsoft MSRC Security Update Guide
  • Tags:

15. CVE-2026-114148 ASP.NET Core Elevation of Privilege Vulnerability

  • Category: Security / Patch
  • What happened: A vulnerability in ASP.NET Core allows an authorized attacker to elevate privileges locally due to incorrect default permissions.
  • Do this Monday: Upgrade ASP.NET Core to the latest version to mitigate the privilege escalation risk.
  • Source: Microsoft MSRC Security Update Guide
  • Tags:

16. ARMORY CASTLE used a BeyondTrust Remote Support zero-day (CVE-2026-102764) since late August - apply BT26-05 and rebuild exposed appliances

  • Category: Security / Patch
  • What happened: The article discusses the zero-day exploitation of BeyondTrust Remote Support CVE-2026-102764 attributed to the PRC-nexus group ARMORY CASTLE. The exploitation involved deploying a webshell and a SOCKS5 tunneler, escalating privileges, harvesting credentials, and deleting logs.
  • Why it matters: Upgrade BeyondTrust Remote Support to the latest version to mitigate CVE-2026-102764.
  • Do this Monday: Self-hosted Remote Support 24.3.1 through 26.2.3: apply the BT26-05-RS patch from /appliance (older versions must upgrade first); SaaS tenants were patched on Oct 9. Treat any internet-reachable appliance that was unpatched since late August as compromised: snapshot it with memory and collect syslog, WAF and firewall logs first (the actor deleted on-appliance logs), redeploy from a clean patched image rather than cleaning in place, and rotate credentials only after the rebuild. Check /login for Jump Item or Team roles raised to Administrator and for API accounts you did not create.
  • Sources: Google Threat Intelligence Group, Canadian Centre for Cyber Security AL26-025
  • Tags:

Releases

17. Kubeflow: KFP SDK 2.18.0, v2.18.0

  • Category: Release
  • What happened: Kubeflow Pipelines 2.18.0 and its corresponding SDK have been released with enhancements to pipeline inspection, authoring, and data management capabilities. The platform now supports automatic artifact previews, clearer visualizations, and data export/import functionality, while the SDK enables local pipeline visualization and component output previews without requiring server deployment. Operators running Kubeflow Pipelines can upgrade to version 2.18.0 to access the new optional retention policies for pipeline data and improved controls for task retries and caching behavior. The local preview capability in SDK v2.18.0 allows developers to validate pipeline definitions and component interfaces before deployment to production clusters.
  • Do this Monday: Upgrade to Kubeflow Pipelines 2.18 to utilize new features and security enhancements.
  • Sources: Kubeflow Pipelines releases, Kubeflow Pipelines releases (2)
  • Tags:

18. Tailscale SSH: the 'Tailworm' report's permission bugs are fixed in 1.104.4 (TS-2026-014 to TS-2026-017)

  • Category: Security / Patch
  • What happened: A researcher report published Oct 24 found that an already-authenticated Tailscale SSH session could act beyond its configured local user's privileges, including through SSH forwarding; exploitation needs a foothold on a tailnet peer that the policy file already allows to SSH in, so unauthenticated attackers cannot reach arbitrary servers. Three of five Serve and Funnel findings were bugs, two are documented behaviour, and the Conn25 app-connector issue is in unreleased code. Tailscale posted its findings on Oct 28 under bulletins TS-2026-014 through TS-2026-017.
  • Why it matters: Upgrade Tailscale to version 1.104.4 to apply the latest SSH fixes.
  • Do this Monday: Update tailscaled to 1.104.4 or later on every node that runs Tailscale SSH, Serve or Funnel. Then tighten the ssh rules in the policy file to the users and devices that need them and consider check mode for sensitive hosts, which asks for a fresh authentication before granting access.
  • Sources: Tailscale findings and fixes, Tailscale investigation update (Oct 26)
  • Tags:

Also this week

Community reads

19. eMudhra CA compromise: the Mozilla post-incident thread, a week after it led this brief

  • Category: Community
  • What happened: eMudhra, a certificate authority, has suffered a private key compromise affecting its intermediate certificates, as documented in Mozilla Bugzilla issue 2083449. Operators should immediately check if any of their TLS certificates chain up to eMudhra intermediate CAs by examining certificate chains in use across their infrastructure. If eMudhra certificates are found, operators need to revoke affected certificates and reissue them from a different certificate authority, as the compromised private keys could allow attackers to issue fraudulent certificates that browsers and systems would initially trust. Mozilla and other browser vendors are expected to distrust the compromised intermediates through root store updates, which will cause service disruptions for any systems still using certificates issued by these intermediates.
  • Why it matters: No action; informational: a private key compromise has been reported.
  • Do this Monday: Nothing new if you worked through last week's lead (linked below). If not, that entry has the ca-certificates and language-bundle versions; this week's GitLab (19.5.3, 19.4.5, 19.3.7, 19.2.10) and Node.js (22.23.4, 24.22.1, 26.12.1) releases also ship the distrust.
  • Sources: Mozilla Bugzilla 2083449, Last week's lead story, emudhra.we-have-a-problem.com
  • Tags:

20. DepGate – an open-source "repository firewall" that blocks malicious packages at install time, across 8 ecosystems

  • Category: Community
  • What happened: DepGate is an open-source 'repository firewall' designed to block malicious packages during installation across multiple ecosystems like npm, PyPI, and Maven. It acts as a proxy that checks requests against a malware feed and user-defined policies before allowing package downloads. Features include known malware prevention, readable policies, a monitor mode for testing, dependency-confusion protection, and a decision ledger for tracking blocks. It is self-hosted and runs on a single Docker image.
  • Why it matters: Consider implementing DepGate as a proxy for your package managers to enhance security against malicious packages.
  • Sources: Reddit r/devops
  • Tags:

Status pages & maintenance

21. GitHub Incident: Dependabot Alerts Degradation and Errors Resolved

  • Category: Status Page
  • What happened: GitHub experienced a service incident affecting Dependabot alerts, leading to elevated errors and performance degradation. The issue has been resolved, and a root cause analysis will be shared later.
  • Takeaway: Incident resolved with monitoring in place.
  • Source: GitHub Status
  • Tags:

22. Claude: 3 service incidents (Elevated errors for Claude Fable 5.1, +2 more)

  • Category: Status Page
  • What happened: Anthropic experienced three separate service disruptions affecting different components of their Claude platform. Claude Fable 5.1 encountered elevated error rates from 08:08 to 08:29 UTC on October 25, which was resolved after deploying a fix. The Gmail connector on claude.ai experienced elevated errors affecting email search and reading functionality from October 27 to October 28, with other connectors remaining unaffected and the issue now resolved. Additionally, Claude Sonnet 5.5 and other unspecified models experienced elevated errors, with a fix deployed and recovery monitoring underway. Operators should verify that API calls and integrations are functioning normally following these incidents, though no configuration changes or upgrades are required as the fixes were applied service-side.
  • Takeaway: Resolved incident with no ongoing impact.
  • Sources: Anthropic Status, Anthropic Status (2), Anthropic Status (3)
  • Tags:

23. Cloudflare: 67 scheduled maintenance windows (Newark, Kanpur, Islamabad, +36 more)

  • Category: Status Page
  • What happened: Cloudflare has scheduled datacenter maintenance across 40+ locations globally between October 25, 2026 and November 6, 2026, with windows ranging from 2 to 34 hours depending on the facility. During these maintenance periods, traffic will be automatically rerouted to other datacenters, which may cause increased latency for regional users, and customers with Private Network Interconnect (PNI) or Cloudflare Network Interconnect (CNI) should prepare for potential traffic failover events as network interfaces may become temporarily unavailable. Notable long-duration windows include QRO (Queretaro) from October 29 08:00 to October 30 18:00 UTC, DFW (Dallas) on October 29 from 07:00 to 17:00 UTC, and multiple AMS (Amsterdam) windows throughout the period. Additionally, Cloudflare will perform storage system maintenance (date unspecified) that will prevent configuration changes via Dashboard or public API for up to 3 minutes, affecting Custom Pages API, Workers Builds, and Log Push services. No operator intervention is required beyond monitoring for traffic failover on PNI/CNI connections and deferring non-critical configuration changes during the storage maintenance window.
  • Heads up: Operators should anticipate increased latency and possible traffic rerouting during the maintenance window. PNI/CNI customers need to ensure their systems can handle traffic failover due to potential unavailability of network interfaces.
  • Sources: Cloudflare Status, Cloudflare Status (2), Cloudflare Status (3) (+64 more)
  • Tags:

Human Stories

The LiteLLM PyPI compromise and the ci-sync branch campaign both exploited trust in ways that feel uncomfortably similar - attackers didn't break down the door, they walked through it wearing the right badge. What strikes me looking across these incidents is how often our defenses assume good faith at the wrong layer: GitHub's run hold protects public repos but leaves private ones exposed, Firebase's routine cleanup lacked the guardrails that would catch a reference break, and AI coding agents happily ingest instructions from whatever markdown file happens to be sitting in Downloads. The eMudhra CA compromise and the stream of service degradations from GitHub and Claude remind us that even when we get our trust boundaries right, the sheer complexity of our systems means something is always one routine operation away from unexpected failure. We keep building more sophisticated tools and tighter integrations, but every new capability is also a new surface where an assumption about trust, isolation, or state can turn a minor mistake into credential exfiltration or a global outage.

Also worth reading

Agents don't go rogue. Scopes do. Five controls, in config (dev.to (Kubernetes tag))

The article discusses the risks associated with AI agents and emphasizes the importance of implementing strict access controls to prevent incidents. It highlights a recent incident involving OpenAI and Hugging Face, where agents exploited vulnerabilities due to inadequate safeguards. The author outl

Quebrei meu próprio sistema de propósito (e foi a melhor decisão da sprint) (dev.to (SRE tag))

The article discusses the importance of Chaos Engineering in distributed systems, highlighting how a slow dependency can cause failures that are harder to detect than outright crashes. It emphasizes the need for a mindset shift from preventing failures to understanding and managing them when they oc

Why Are Grocery Store Refrigerators Connected to the Internet? (Security Boulevard)

An attack on French supermarket refrigeration systems highlights the risks associated with connected physical operations, which rely on long-lifecycle equipment and complex vendor access, leading to significant real-world consequences when security controls fail.