The week: Ruby fixes seven memory flaws, Cloudflare versions expire, Supabase merge tokens
สรุปสัปดาห์ 16 พฤศจิกายน: Ruby แก้ช่องโหว่หน่วยความจำเจ็ดรายการ Cloudflare ลบเวอร์ชันที่เก่ากว่า 30 วัน และการ merge branch ของ Supabase ต้องใช้โทเค็นสิทธิ์ production
Six notes, from a reasoning switch that still bills to a domain moved with one line. Plus five outside items: Ruby 4.0.10, 3.4.13 and 3.3.14, Cloudflare's 30-day version retention, and three billing and limit changes.
Ruby 4.0.10, 3.4.13 and 3.3.14 came out on 18 November 2026 with fixes for seven memory flaws in two everyday operations: changing the case of a string and handling a regular expression (a search pattern) 1. The Ruby team writes that it knows of proofs of concept that reach remote code execution, an attacker running their own code on the server, for some of them 1. That leads the five outside items. First, the week's six notes.
Six notes, 16 to 21 November
Monday, models. Inkling 2 Small on Workers AI: reasoning_effort none still thinks, and bills for it: Cloudflare added Thinking Machines' open model on 12 November and said none turns reasoning off (reasoning is the working a model writes before its answer, billed as output). In 300 graded calls, none reasoned in 30 of 30 replies and used 16% more output tokens than the default. minimal got 30 of 30 right with 34% fewer tokens than the default. enable_thinking: false did switch reasoning off, and 19 of 30 answers were right.
Tuesday, last-mile. Supabase turned off four TLS 1.2 ciphers: 9 of 163 recorded clients now fail to connect: the removal announced for 10 November is in effect on project APIs. We replayed the opening message of 163 recorded browsers and runtimes. Safari 5 to 8, Chrome 30 and Opera 17 fail before they send a request, so nothing shows in the project's logs. IE 11 connects because one of the project's two certificates is ECDSA. Two openssl commands in the note test a project or a custom domain.
Wednesday, security. OpenSSH 10.6p2 shut the 300-byte password bypass on Alpine sshd: on Alpine Linux, a password 256 to 1,024 bytes long logged into accounts whose password field was *, the mark for a locked account. OpenSSH 10.6p2 of 5 November refuses the comparison, and CISA listed the flaw as exploited on 9 November. All eight Alpine branches we read carried the fixed package. PasswordAuthentication no closes the path without an upgrade.
Thursday, automation. n8n 2.48.4 and 2.47.7 stop blanking the execution page for a global credential: a run that used a global credential, one shared with every user of the installation, came back as "Data redacted" with no reveal button, even for the person who ran it. The fix shipped on 13 November in both lines and on 17 November in 2.49.0. Redaction set per workflow or by the instance works as before.
Friday, models. Order tickets from four open models: symbol codes silently wrong 186 times in 660, JSON 46: a paper from ITMO University reports that a ticket's format changes how often a small model writes a valid ticket for the wrong order. We prompted four models on Workers AI with 60 drink orders in four formats. Symbol codes did worst on all four models, JSON best. A short word check caught 28 of JSON's 46 silent errors, and Llama 4 Scout wrote 360 of 360 JSON tickets right.
Saturday, last-mile. One Cloudflare Pages line moved a domain: 147 of 147 URLs in one hop, POSTs become GETs: one _redirects line sends each old path and its query string to the new address. Without 301 at the end the line answers 302, the temporary code. A 301 turns a form's POST into a GET, so forms and webhooks need their own receiver. The note has a 16-line check and the conditions of Google's Change of Address tool.
Five items, 12 to 20 November
18 November: Ruby 4.0.10, 3.4.13 and 3.3.14. Six of the seven flaws are in the advisory as possible remote code execution; the seventh discloses memory or crashes the process 1. Two sit in case conversion, the code behind calls such as upcase and downcase: changing the case of a crafted string is the trigger 1. Four need an attacker-controlled pattern, as in a search box that accepts regular expressions 1. Affected: 3.3.13 and earlier, 3.4.0 to 3.4.12, 4.0.0 to 4.0.9; Ruby 3.2 and older get no fix 1. CVE numbers were requested and not yet assigned on the advisory, which uses GitHub advisory IDs 1. Cloudflare added two Ruby rules on 19 November, a heap overflow and an integer overflow, with the action Block in its Free and Managed rulesets 2. Docker Hub's record for the official ruby:4.0.10 image, read 22 November, is dated 19 November 00:49 UTC 3; the records for 3.4.13, 3.3.14, 4.0, 3.4 and latest carry the same date. A Dockerfile with FROM ruby:3.4 gets the fix on docker build --pull; one pinned to ruby:3.4.12 needs the new number. ruby -v prints the running version.
19 November: Cloudflare deletes Worker versions and Pages deployments after 30 days. A version is each upload of a Worker's code or change to its settings. After 30 days it goes, unless it is one of the 100 most recent or is deployed now 45. Pages follows the same count, with production and preview deployments counted together and the current production deployment exempt 6. A deleted version's Version URL stops working, as does a deleted Pages deployment's preview URL at <hash>.<project>.pages.dev 56. A preview link in an email to a client, a ticket or a slide is the casualty. Rollback reaches the 100 most recent Worker versions 5. For a link that lasts, Cloudflare points to Worker Previews, whose URL serves the latest deployment of that preview 4.
12 November: merging a Supabase branch needs a production token. A branch is a separate copy of a project for testing changes. Since 12 November, merging one into the main project needs a scoped personal access token with Production Branches: Read-write; a token with Development Branches access alone gets a permission error from the merge call and from the MCP merge_branch tool that AI agents use 7. Classic personal access tokens are unaffected 7. An existing token's permissions cannot be edited, so the merge step in CI needs a new token 7. Supabase plans a separate Merge permission later 7. The page went up on 16 November, four days after the change 7.
17 November: new Vercel teams pay for Standard builds by the minute. New Pro and Enterprise teams no longer include a Standard build slot 8. On Pro a Standard build costs US$0.014 per build minute, and the monthly usage credit applies 8. By that rate, 20 three-minute builds a day for 30 days is 1,800 minutes, US$25.20. The page speaks of new teams; it says nothing about teams created before 17 November 8.
20 November: Vercel Functions accept request bodies up to 20 MiB, in public beta. The limit was 4.5 MB 9. The opt-in is the environment variable VERCEL_SUPPORT_LARGE_REQUEST_BODY=1, per project and per environment, and it requires the performance memory setting of 4 GB 9. It covers the Node.js, Python and Bun runtimes; the Edge runtime stays at 4.5 MB and answers 413 to a larger body 9. With the opt-in on, Routing Middleware (code that runs before the function) receives headers and no body, so middleware that reads the body stops seeing it 9.
Sources
- Security advisories: multiple vulnerabilities in Regexp and String case conversion · Ruby, 18 November 2026 ruby-lang.org
- WAF Emergency Release - 2026-11-19 · Cloudflare changelog developers.cloudflare.com
- ruby 4.0.10 · Docker Hub tag record hub.docker.com
- Workers and Pages now keep versions for 30 days · Cloudflare changelog, 19 November 2026 developers.cloudflare.com
- Versions & Deployments · Cloudflare Workers docs developers.cloudflare.com
- Limits · Cloudflare Pages docs developers.cloudflare.com
- Merging a branch now requires Production Branches read-write · Supabase changelog, 16 November 2026 supabase.com
- Standard builds move to usage-based billing for new teams · Vercel changelog, 17 November 2026 vercel.com
- Vercel Functions now support request bodies up to 20MiB · Vercel changelog, 20 November 2026 vercel.com
Hongdam Studio services on this topic
- Website maintenanceUpdates, backups, an alert if your site stops working, and 2 hours of fixes a month.฿3,000 / monthBuy
- Finish my vibe codeAn app or site made with an AI tool such as Lovable, Bolt, Replit or Cursor: we read it, fix it and publish it.from ฿5,000Buy
- Hacked site cleanupWe remove malware (harmful software), fix the weakness the attacker used, and write a report.฿5,000 / siteBuy
- AI assistant with your name on itYour own chat assistant. It answers from your web pages, and your staff can log in.from ฿20,000Buy