Brotli Bug: Not Just Node.js | Dev News Oct 25, 2026
The developer stories you need from the weekend, in four minutes: what happened, why it matters, and what to do. 1. Wednesday's Node.js Brotli bug reaches Python, Bun, Envoy and Istio. Run pip show brotli everywhere; upgrade Brotli to 1.2.1 and brotlicffi to 1.2.1.0, Bun to 1.4.4, and patch Envoy or Istio if Brotli decompression is on. Then rebuild your images. 2. LiteLLM's post-mortem: a key leaked in May and not revoked led to the hijacked 1.107.0 release. Installed it? Rebuild from scratch, pin 1.106.2, rotate every secret. 3. PHP2Shell: Palo Alto's firewall fixes are due Oct 26 to Oct 30, depending on the version. Patch PHP (8.5.12, 8.4.27, 8.3.36, 8.2.35); on PAN-OS, lock down the management interface until your hotfix arrives. 4. Ruby 4.0.9, 3.4.12 and 3.3.13 fix the regex bugs behind four GitLab CVEs. Never compile regexes from untrusted input. 5. Kimi K3.1 Pro: within a point of Claude Opus 5.5 on Terminal-Bench (Moonshot's numbers), open weights promised by Nov 4.
Chapters
- 0:00 Intro
- 0:15 Today's rundown
- 0:47 Brotli, beyond Node
- 1:49 LiteLLM's leaked key
- 2:40 PHP2Shell update
- 3:04 Ruby's regex fixes
- 3:33 Kimi K3.1 Pro
- 4:11 Sign-off
Sources
- Node.js security releases (Oct 21)
- GitHub advisory for the Python packages
- Aikido (Python impact)
- Imperva (Node RCE, Oct 22)
- The Hacker News (Oct 24)
- Brotli releases
- Bun 1.4.4
- Envoy advisory
- Istio bulletin
- LiteLLM attack chain (Oct 23)
- LiteLLM incident post
- Microsoft on LiteLLM 1.107.0 (Oct 23)
- Palo Alto advisory
- Ruby regexp fixes (Oct 23)
- GitLab patch release (CVE-2026-97229)
- Kimi K3.1 Pro
- Artificial Analysis (Oct 23)
Transcript
On Wednesday, Node.js fixed a serious bug in its Brotli decompressor. Now it turns out the same bug reaches Python, Bun and Envoy. And the fix had been sitting in Brotli's code since February.
This is Just Known Daily, for Sunday, October 25th. Five stories today. Wednesday's Node.js bug turns out to reach Python, Bun and Envoy. LiteLLM explains how one leaked key led to its hijacked release. Palo Alto sets dates for its PHP2Shell fixes.
Ruby patches the regex bugs behind GitLab's critical flaws. And Kimi K3.1 Pro closes in on the top coding models. On Wednesday, Node.js patched a high-severity bug in its Brotli decompressor. It turns out the bug isn't Node's. It's in Brotli itself, Google's compression library, and a lot of software ships the same decoder.
Python's Brotli and brotlicffi packages, Bun, Envoy and Istio have all shipped fixes. In Python, you don't even have to import it. If the package is installed, requests, httpx and aiohttp use it to decode compressed responses automatically. How bad is it? In Node, researchers at Imperva turned it into remote code execution, though it took several attempts.
For the Python packages, researchers confirmed the bug but haven't tried to exploit it. And the fix itself had been sitting in Brotli's code since February, with no Brotli release until this week. So check by hand. Run pip show brotli in every environment and image, upgrade to 1.2.1, update Bun to 1.4.4, and patch Envoy or Istio if you turned on Brotli decompression. Next, LiteLLM, the popular Python library for calling AI models, explained on Friday how Wednesday's release got hijacked.
It started in May, when a master key was committed to a public repo. The team force-pushed over it, but didn't revoke the key. In October, the attacker used that key to reach an owner's GitHub token, then stole two maintainers' tokens through CI. And earlier that week, the release rule had been relaxed so that any two engineers could trigger and approve one. So one stolen token triggered the release, and another approved it.
The bad version was on PyPI for under two hours, and its startup hooks run every time Python starts. If you installed it, rebuild from scratch and rotate every secret that machine could reach. And remember: deleting a leaked key from git doesn't un-leak it. Revoke it. A quick update on PHP2Shell, the critical PHP flaws from this week.
Palo Alto's firewall fixes are now due from Monday through Friday, depending on the version. The exposure is through the management interface, so keep it locked down until your hotfix arrives. Palo Alto says it isn't aware of attacks on its own products. If you still haven't patched PHP, today is the day. On Friday, Ruby shipped fixes for 4.0, 3.4 and 3.3, for three bugs in its regex engine.
GitLab reported them: they're behind four GitLab CVEs, including this month's flaw rated a perfect ten, and GitLab found they could be used to run code on GitLab servers. You're exposed if your app builds a regex from user input. A timeout doesn't help. So upgrade Ruby, and until you can, don't compile regexes from untrusted input. And in AI, Moonshot released Kimi K3.1 Pro, a model it says is within a point of Claude Opus 5.5 on Terminal-Bench.
Those are Moonshot's own numbers, but the independent Artificial Analysis index also ranks it fourth overall. It costs two dollars per million input tokens, with a one-million-token context. The bigger news: Moonshot says the full weights will be out by November 4th. That would make it the strongest open-weights model, by Artificial Analysis's count. Try it on your own agent tasks through the API, and wait for the weights and a license before you plan to self-host.
That's what's known today. Every source is linked in the description. This is Just Known Daily. From unknown, to known. See you tomorrow.
Narration voice generated with Google Gemini text-to-speech.
