CVE-2026-125111 (High) detected in rack-3.1.16.gem
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 58/100
Rechercherichtung
Start with the dependency entry in Gemfile.lock and identify how rack 3.1.16 is included through rubocop-rails. The report says Rack 3.1.23 fixes the multipart parser vulnerability; check the project's dependency constraints and update path, then confirm the resolved Rack version is fixed. The issue names no tests or other files to guide verification.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
CVE-2026-125111 - High Severity Vulnerability
Vulnerable Library - rack-3.1.16.gem
Rack provides a minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call.
Library home page: https://rubygems.org/gems/rack-3.1.16.gem
Sample Path to Dependency File: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-3.1.16.gem
Dependency Hierarchy:
- manageiq-style-1.3.3.gem (Root Library)
- rubocop-rails-2.32.0.gem
- ❌ rack-3.1.16.gem (Vulnerable Library)
- rubocop-rails-2.32.0.gem
Found in base branch: master
Vulnerability Details
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser can retain parsed data in its internal StringScanner buffer when reads end inside or immediately after multipart headers. An unauthenticated attacker can align many small parts with rack.multipart.buffer_size boundaries so the buffer grows with the request despite per-field, header, and preamble limits, causing a worker to exhaust memory. The attack requires only a well-formed multipart body and affects applications that parse multipart requests. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
Publish Date: 2026-11-09
URL: CVE-2026-125111
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Release Date: 2026-11-09
Fix Resolution: rack - 3.1.23
Step up your Open Source Security Game with Mend here
- Vorherrschende Sprache
- Ruby
- Sterne
- 30
- Forks
- 27
- Ø Merge
- 1 Std. 31 Min.
- Gemergte PRs (30 T.)
- 3
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus ManageIQ/linux_admin
-
Mend: dependency security vulnerability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
ManageIQ/linux_admin#296 ·
-
Mend: dependency security vulnerability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ManageIQ/linux_admin#291 ·
-
Mend: dependency security vulnerability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
ManageIQ/linux_admin#290 ·
-
Mend: dependency security vulnerability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
ManageIQ/linux_admin#289 ·
-
Mend: dependency security vulnerability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ManageIQ/linux_admin#288 ·
Alle Issues in ManageIQ/linux_admin
Ähnliche Issues
-
Bug Ruby
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
getsentry/sentry-ruby#3211 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
internetee/registry#2984 ·
Maintainer antworten meist innerhalb von 6 Tagen
-
interest-zsv
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
hitobito/hitobito_zsv#6 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
ecosyste-ms/issues#862 ·
Maintainer antworten meist innerhalb von 1 Tag