🚨 [security] Update rails 8.0.2.1 → 8.0.5 (minor)#584
Merged
akostadinov merged 4 commits intomasterfrom Apr 1, 2026
Merged
Conversation
jlledom
force-pushed
the
depfu/update/group/rails-8.0.5
branch
from
fda6d15 to
f23ead4
Compare
It's now a separated dependency
jlledom
force-pushed
the
depfu/update/group/rails-8.0.5
branch
from
f23ead4 to
b70cc51
Compare
Contributor
|
I've been working on this update, I had to upgrade several gems and check several others that got major updates in this PR. This is the summary, written by Claude:
|
josemigallas
reviewed
Apr 1, 2026
| group :test do | ||
| gem 'minitest-reporters' | ||
| gem 'minitest-stub-const' | ||
| gem "minitest-mock", "~> 5.27" |
Contributor
There was a problem hiding this comment.
This one smells like a dependency that is no longer included by one of the upgraded ones?
Contributor
There was a problem hiding this comment.
akostadinov
approved these changes
Apr 1, 2026
Contributor
akostadinov
left a comment
akostadinov
left a comment
There was a problem hiding this comment.
Do we really need to update puma and minitest to upgrade rails? I guess depfu added more stuff than needed. Anyway, thank you for looking into this. We need to keep stuff updated anyway so looks good!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: https://redhat.atlassian.net/browse/THREESCALE-14266
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rails (8.0.2.1 → 8.0.5) · Repo · Changelog
Release Notes
8.0.4.1
8.0.4
8.0.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Rails has a possible XSS vulnerability in its Action View tag helpers
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Rails Active Storage has a possible DoS vulnerability in proxy mode via multi-range requests
🚨 Rails Active Storage has possible content type bypass via metadata in direct uploads
🚨 Rails Active Storage has a possible DoS vulnerability when in proxy mode via Range requests
🚨 Rails Active Storage has possible Path Traversal in DiskService
🚨 Rails Active Storage has possible glob injection in its DiskService
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Rails Active Support has a possible ReDoS vulnerability in number_to_delimited
🚨 Rails Active Support has a possible XSS vulnerability in SafeBuffer#%
🚨 Rails Active Support has a possible DoS vulnerability in its number helpers
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
6.0.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.17.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Improper detection of disallowed URIs by Loofah `allowed_uri?`
Release Notes
2.25.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
6.0.2 (from changelog)
6.0.1 (from changelog)
6.0.0 (from changelog)
5.27.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.6.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.19.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Rack has a Directory Traversal via Rack:Directory
🚨 Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href
🚨 Rack has a Directory Traversal via Rack:Directory
🚨 Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href
🚨 Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing
🚨 Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing
🚨 Rack has a Possible Information Disclosure Vulnerability
🚨 Rack has a Possible Information Disclosure Vulnerability
🚨 Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
🚨 Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)
🚨 Rack: Multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)
🚨 Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
🚨 Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)
🚨 Rack: Multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)
🚨 ReDoS Vulnerability in Rack::Multipart handle_mime_head
🚨 Rack has an Unbounded-Parameter DoS in Rack::QueryParser
🚨 Rack has an Unbounded-Parameter DoS in Rack::QueryParser
🚨 Local File Inclusion in Rack::Static
🚨 Local File Inclusion in Rack::Static
🚨 Escape Sequence Injection vulnerability in Rack lead to Possible Log Injection
🚨 Escape Sequence Injection vulnerability in Rack lead to Possible Log Injection
🚨 Possible Log Injection in Rack::CommonLogger
🚨 Rack ReDoS Vulnerability in HTTP Accept Headers Parsing
🚨 Rack has possible DoS Vulnerability with Range Header
🚨 Rack Header Parsing leads to Possible Denial of Service Vulnerability
🚨 Rack vulnerable to ReDoS in content type parsing (2nd degree polynomial)
🚨 Possible Denial of Service Vulnerability in Rack's header parsing
🚨 Rack has possible DoS Vulnerability in Multipart MIME parsing
🚨 Denial of Service Vulnerability in Rack Content-Disposition parsing
🚨 Denial of service via header parsing in Rack
🚨 Denial of service via multipart parsing in Rack
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Rack session gets restored after deletion
Release Notes
2.1.1
2.1.0
2.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
7.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Security Advisories 🚨
🚨 Sinatra is vulnerable to ReDoS through ETag header value generation
🚨 Sinatra vulnerable to Reliance on Untrusted Inputs in a Security Decision
🚨 Sinatra vulnerable to Reflected File Download attack
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.6.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands