Simon,

On Wednesday, November 18, 2026 10:07:10 AM Mountain Standard Time Simon 
Quigley wrote:
> Source: rails
> Version: 2:7.2.4+dfsg-2
> Severity: grave
> Tags: security upstream sid forky trixie bookworm
> Owner: Simon Quigley <[email protected]>
> X-Debbugs-Cc: Debian Security Team <[email protected]>, Debian Ruby
> Team <[email protected]>
 
> 18 CVEs have been published for Rails, they are:
> 
>   - CVE-2026-126188:
> https://security-tracker.debian.org/tracker/CVE-2026-126188
 -
> CVE-2026-126186: https://security-tracker.debian.org/tracker/CVE-2026-126186
> - CVE-2026-126085:
> https://security-tracker.debian.org/tracker/CVE-2026-126085 -
> CVE-2026-126084: https://security-tracker.debian.org/tracker/CVE-2026-126084
> - CVE-2026-126081:
> https://security-tracker.debian.org/tracker/CVE-2026-126081 -
> CVE-2026-126080: https://security-tracker.debian.org/tracker/CVE-2026-126080
> - CVE-2026-126079:
> https://security-tracker.debian.org/tracker/CVE-2026-126079 -
> CVE-2026-126078: https://security-tracker.debian.org/tracker/CVE-2026-126078
> - CVE-2026-126077:
> https://security-tracker.debian.org/tracker/CVE-2026-126077 -
> CVE-2026-126076: https://security-tracker.debian.org/tracker/CVE-2026-126076
> - CVE-2026-126074:
> https://security-tracker.debian.org/tracker/CVE-2026-126074 -
> CVE-2026-126073: https://security-tracker.debian.org/tracker/CVE-2026-126073
> - CVE-2026-126072:
> https://security-tracker.debian.org/tracker/CVE-2026-126072 -
> CVE-2026-126070: https://security-tracker.debian.org/tracker/CVE-2026-126070
> - CVE-2026-126069:
> https://security-tracker.debian.org/tracker/CVE-2026-126069 -
> CVE-2026-126068: https://security-tracker.debian.org/tracker/CVE-2026-126068
> - CVE-2026-126067:
> https://security-tracker.debian.org/tracker/CVE-2026-126067 -
> CVE-2026-122006: https://security-tracker.debian.org/tracker/CVE-2026-122006 
> I have not yet determined whether 7.2.4, or older versions, are affected by
> these CVEs. There are no upstream fixes available for 7.2.4, so backports
> will be required.
 
> I will take ownership of this bug to start, and get the fixes in for 
Unstable
> by the end of this weekend, along with a triage here (so by end of day on
> November 22nd, 2026). Then, Trixie comes next, with Bookworm coming at about
> the same time. My rough ETA for those two suites at this point is one week
> (so by November 25th, 2026).
 
> If anyone is motivated to work on patches earlier for any of the suites
> mentioned, all I would ask is that you keep me and this bug updated. Help is
> absolutely welcome.

Thanks for taking this on.  I don’t have the time to assist, but I appreciate 
what you are doing.

> Big picture, I don't personally think we're ready for Rails 8 at this 
current
> moment, but in an ideal world it would happen for Forky.

I agree that it would be best to ship Rails 8 in Forky.  I think it would make 
it easier to manage security support while Forky is stable.

-- 
Soren Stoutner
[email protected]

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to