FoxIO found seven of ten HTTP/3 stacks open to header amplification. quic-go, Cloudflare quiche, lsquic and Wireshark are fixed; Bun, the h3 crate and aioquic are not, and a proof of concept is public.
Rails 8.0.5.2 and 8.1.4.1 fix 21 flaws as 8.0 support nears its end
EditorialBy TrustList Editorial
One critical Active Storage flaw allows arbitrary file reads and writes during image analysis, and four more are rated high. Security support for Rails 8.0 ends on 7 November, so 8.0 apps should plan the move to 8.1.
- Cybersecurity
- Web Development
- Patch Management
About Rails 8.0.5.2 and 8.1.4.1 fix 21 flaws as 8.0 support nears its end
Rails 8.0.5.2 and 8.1.4.1 fix 21 flaws as 8.0 support nears its end
4 November 2026: The Ruby on Rails core team has released Rails 8.0.5.2 and 8.1.4.1 with fixes for 21 security issues, one of them critical, and says it strongly recommends upgrading as soon as possible. The same post sets a deadline: security support for the Rails 8.0 series ends on 7 November 2026, three days after the release, and versions older than 8.0 are already unsupported.
Not yet independently verified. The Rails post lists GitHub advisory identifiers rather than CVE numbers, and we have not opened each advisory; it makes no claim of exploitation. We will update this when it can be confirmed, and remove this note.
The critical and high-rated fixes
The release post, written by Mike Dalessio, lists the issues by GitHub advisory identifier:
- critical, GHSA-f3w6-w445-fwh9: arbitrary file write and read in Active Storage image analysis;
- high, GHSA-v924-7rp8-4mxh: arbitrary file read and remote code execution in Active Storage video previews, analysis and image processing;
- high, GHSA-wm3x-v3qw-4jh3: a Strong Parameters bypass through Parameters#each_key;
- high, GHSA-2gff-2mmg-m73p: IP address spoofing in Action Dispatch's RemoteIp through the Forwarded header, in 8.1 only;
- high, GHSA-8474-xrp6-wh69: denial of service in Active Support's safe_constantize.
Two of the top three sit in Active Storage, the part of Rails that handles uploaded files, which is exactly where attacker-supplied content enters an application.
The rest of the list
The medium and low issues cover cross-site scripting in Action View's text, highlight, strip_tags and tag helpers and in Active Support's MessagePack serializer (8.1 only); denial of service in Action Controller Live and in Active Storage's proxy and filename handling; an unsigned Content-Type and an unenforced size limit for direct uploads to Google Cloud Storage; a destroyed session that CacheStore could restore; a session cookie leak in Active Storage proxy mode; missing SameSite attributes on session cookies; cache poisoning through content negotiation; and signature replay in Action Mailbox's Mailgun ingress.
Upgrade order for Rails teams
- Apps on 8.1 should move to 8.1.4.1 now.
- Apps on 8.0 should take 8.0.5.2 now and schedule the move to 8.1, since fixes after 7 November will not be backported to 8.0.
- Apps on 7.x or older get none of these fixes and have no supported upgrade path short of moving to 8.0 or later.
- Apps that process uploads with Active Storage, especially image and video analysis, should treat the critical and first high fix as the priority and check the libraries they call for analysis and previews.
Sources
- Ruby on Rails blog: Rails 8.0.5.2 and 8.1.4.1 have been released, 4 November 2026
Categories & features
- Cybersecurity
- Web Development
- Patch Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
CVE-2026-114509 lets an attacker with no token log in as an existing user on apps using TokenGuard with MySQL or MariaDB. Upgrade to 13.29.0 or 12.68.0; a proof of concept is public.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 close CVE-2026-109618 and CVE-2026-109619. Every PHP install serving web requests is at risk, mod_php most of all, and PHP 8.1 and older get no official fix.
Nine advisories published on 5 October cover four high-severity code execution paths through the Twig sandbox; Canada's Cyber Centre urged updates on 20 October. The fixes have been out since 1 September.
SA-CORE-2026-014 scores 19 out of 25. Sites on 11.2 or 10.5 and older have no patch; uninstalling the Field UI module blocks the flaw until an upgrade is possible.
The alias and rewrite overflow affects every release since 0.1.29. The fix release also moves HTTP/2 to RFC 9218 prioritisation and adds MaxMind DB support to the GeoIP modules.
One flaw sits in image optimisation of SVG files and reaches back to Next.js 10; the other hits the use cache directive in 16.x and has no workaround. A third advisory fixes a Server Actions denial of service.
Neither bulletin reports exploitation, but ColdFusion servers have been attacked soon after past patch days; AEM 6.5 customers must apply named hotfixes on top of their service pack.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.