# Well, That Wasn't Fun: October 16 '26

DevFeed: [Well, That Wasn't Fun: October 16 '26](<https://devfeed.tech/articles/well-that-wasn-t-fun-october-16-26-121085.md>)

Original publisher: [Read original article](<https://fly.io/blog/well-that-wasnt-fun/>)

Author: Daniel Botha

Published: 2026-11-06T00:00:00Z

Content type: news

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [TCP/IP](<https://devfeed.tech/topics/tcp-ip.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [payload](<https://devfeed.tech/topics/payload.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [based](<https://devfeed.tech/tags/based.md>), [bug](<https://devfeed.tech/tags/bug.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [card](<https://devfeed.tech/tags/card.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [checksums](<https://devfeed.tech/tags/checksums.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [code](<https://devfeed.tech/tags/code.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cve](<https://devfeed.tech/tags/cve.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [example](<https://devfeed.tech/tags/example.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [field](<https://devfeed.tech/tags/field.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [fun](<https://devfeed.tech/tags/fun.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [networking](<https://devfeed.tech/tags/networking.md>), [october](<https://devfeed.tech/tags/october.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>)

## AI overview

Fly.io patched and rebooted its fleet after CVE-2026-99999 exposed a flaw in Linux IPv4 checksum-offload validation for virtual machine traffic. By redirecting checksum writes, an attacker could alter two trusted IPv4 header bytes after routing and firewall checks, enabling a firewall bypass or a 32-byte out-of-bounds read that might expose host or neighboring VM data. Fly.io says it has no evidence customer data was exposed, but advises customers who ran there October 15-17 to rotate credentials sent over unencrypted protocols, including plaintext traffic over 6PN. The 10-hour rollout required staggered host reboots to limit disruption to Managed Postgres clusters; some machines remained down after hardware and reinstall problems, with no machines or customer data lost. Fly.io also revised incident communications so executives own the communication plan. Its practical security guidance includes encrypting internal traffic, using scoped and expiring agent credentials, limiting shared exposure across trust boundaries, treating agent inputs as hostile, and rehearsing credential rotation.

## Source excerpt

October 16, 2026 began like any other day at Fly.io (meaning, we were anticipating only a medium amount of chaos). By that evening, we had patched and rebooted our entire fleet in response to a Linux kernel bug. The full rollout took 10 hours, but the emotional damage persists. CVE-2026-99999 The rest of this won't make much sense without a clear read on the bug itself, so: the Linux kernel CVE team and pwn.ai announced CVE-2026-99999 on the morning of the 15th. We heard about it that night, and started working on mitigations. IP sleight of hand Protocols like TCP and UDP include checksums to detect corruption on the way across the internet. Calculating one means reading the whole message, which adds up at high speeds. Linux avoids that with checksum offload: instead of calculating the checksum immediately, the kernel stores metadata saying where the checksum should read from and write to. If the checksum turns out not to be needed, the kernel never spends the CPU on it. Not needed, for example, when sending to localhost, or when the network card can add its own checksums. Checksum offload works the same way for virtual machines. The virtual network card accepts checksum metadata and passes it to the host. On the host side, the packet is treated like any other offloaded packet, using the metadata the guest provided. The offload code has checks meant to reject bad metadata. For IPv4, they were wrong. To exploit that, an attacker needs to do three things: point the checksum at a different header field, pick a message that produces the checksum they want, and force the host to calculate the checksum in software. The pwn.ai post goes into detail on pulling that off. The end result: the host receives the packet, parses it, decides where to send it, then applies the checksum, in the wrong place. The attacker now controls two bytes of an IPv4 header the host has already trusted. Based on network activity during the rollout, we believe it's unlikely that any of our customer