Is rack 3.0 vulnerable?
RubyGems · 23 releases from 3.0.0 to 3.0.18 · latest rack is 3.2.8 · checked 18 Nov 2026
Yes: 20 known advisories
Yes. rack 3.0.18, the last 3.0 release, is affected by 20 known security advisories (7 high, 12 medium, 1 low), including CVE-2026-125111, CVE-2026-34829, CVE-2026-34230. 12 more affect earlier 3.0.x releases. Upgrade to 3.1.23 or later to fix all of them.
bundle update --conservative rack # Gemfile: '>= 3.1.23'Is your project on an affected rack?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting rack 3.0.18
Rack: Multipart parsing allows DoS via unbounded scan buffer growth
- Affected
- <2.2.25 · >=3.0.0 <3.1.23 · >=3.2.0 <3.2.8
- Fixed in
- 2.2.25, 3.1.23, 3.2.8
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
- Affected
- <2.2.25 · >=3.0.0 <3.1.23 · >=3.2.0 <3.2.8
- Fixed in
- 2.2.25, 3.1.23, 3.2.8
Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835
- Affected
- >=3.0.0 <3.1.23 · >=3.2.0 <3.2.8
- Fixed in
- 3.1.23, 3.2.8
Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch
- Affected
- <2.2.25 · >=3.0.0 <3.1.23 · >=3.2.0 <3.2.8
- Fixed in
- 2.2.25, 3.1.23, 3.2.8
Rack::Request accepts invalid Host characters, enabling host allowlist bypass
- Affected
- >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 3.1.21, 3.2.6
Rack has Content-Length mismatch in Rack::Files error responses
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack::Sendfile header-based X-Accel-Mapping regex injection enables unauthorized X-Accel-Redirect
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack's multipart parsing without Content-Length header allows unbounded chunked file uploads
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack has a root directory disclosure via unescaped regex interpolation in Rack::Directory
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack has quadratic complexity in Rack::Utils.select_best_encoding via wildcard Accept-Encoding header
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack: Forwarded Header semicolon injection enables Host and Scheme spoofing
- Affected
- >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 3.1.21, 3.2.6
Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack's multipart header parsing allows Denial of Service via escape-heavy quoted parameters
- Affected
- >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 3.1.21, 3.2.6
Rack's multipart byte range processing allows denial of service via excessive overlapping ranges
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack:: Static header_rules bypass via URL-encoded paths
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Rack::Static prefix matching can expose unintended files under the static root
- Affected
- <2.2.23 · >=3.0.0.beta1 <3.1.21 · >=3.2.0 <3.2.6
- Fixed in
- 2.2.23, 3.1.21, 3.2.6
Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href
- Affected
- <2.2.22 · >=3.0.0.beta1 <3.1.20 · >=3.2.0 <3.2.5
- Fixed in
- 2.2.22, 3.1.20, 3.2.5
Rack has a Directory Traversal via Rack:Directory
- Affected
- <2.2.22 · >=3.0.0.beta1 <3.1.20 · >=3.2.0 <3.2.5
- Fixed in
- 2.2.22, 3.1.20, 3.2.5
Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing
- Affected
- <2.2.20 · >=3.0 <3.1.18 · >=3.2 <3.2.3
- Fixed in
- 2.2.20, 3.1.18, 3.2.3
Rack has a Possible Information Disclosure Vulnerability
- Affected
- <2.2.20 · >=3.0 <3.1.18 · >=3.2 <3.2.3
- Fixed in
- 2.2.20, 3.1.18, 3.2.3
Fixed within 3.0.x, affecting earlier releases
Rack has an Unbounded-Parameter DoS in Rack::QueryParser
- Affected
- <2.2.14 · >=3.0 <3.0.16 · >=3.1 <3.1.14
- Fixed in
- 2.2.14, 3.0.16, 3.1.14
Local File Inclusion in Rack::Static
- Affected
- <2.2.13 · >=3.0 <3.0.14 · >=3.1 <3.1.12
- Fixed in
- 2.2.13, 3.0.14, 3.1.12
Escape Sequence Injection vulnerability in Rack lead to Possible Log Injection
- Affected
- <2.2.12 · >=3.0 <3.0.13 · >=3.1 <3.1.11
- Fixed in
- 2.2.12, 3.0.13, 3.1.11
Possible Log Injection in Rack::CommonLogger
- Affected
- <2.2.11 · >=3.0 <3.0.12 · >=3.1 <3.1.10
- Fixed in
- 2.2.11, 3.0.12, 3.1.10
Rack vulnerable to ReDoS in content type parsing (2nd degree polynomial)
- Affected
- >=3.0.0 <3.0.9.1 · >=0.4 <2.2.8.1
- Fixed in
- 2.2.8.1, 3.0.9.1
Rack has possible DoS Vulnerability with Range Header
- Affected
- >=3.0.0 <3.0.9.1 · >=1.3.0 <2.2.8.1
- Fixed in
- 2.2.8.1, 3.0.9.1
Rack Header Parsing leads to Possible Denial of Service Vulnerability
- Affected
- >=3.0.0 <3.0.9.1 · >=2.2.0 <2.2.8.1 · >=2.1.0 <2.1.4.4 · <2.0.9.4
- Fixed in
- 2.0.9.4, 2.1.4.4, 2.2.8.1, 3.0.9.1
Possible Denial of Service Vulnerability in Rack's header parsing
- Affected
- >=2.0.0 <2.2.6.4 · >=3.0.0 <3.0.6.1
- Fixed in
- 2.2.6.4, 3.0.6.1
Rack has possible DoS Vulnerability in Multipart MIME parsing
- Affected
- <2.0.9.3 · >=2.1.0 <2.1.4.3 · >=2.2.0 <2.2.6.3 · >=3.0.0 <3.0.4.2
- Fixed in
- 2.0.9.3, 2.1.4.3, 2.2.6.3, 3.0.4.2
Denial of Service Vulnerability in Rack Content-Disposition parsing
- Affected
- >=2.0.0 <2.0.9.2 · >=2.1.0 <2.1.4.2 · >=2.2.0 <2.2.6.1 · >=3.0.0.0 <3.0.4.1
- Fixed in
- 2.0.9.2, 2.1.4.2, 2.2.6.1, 3.0.4.1
Denial of service via header parsing in Rack
- Affected
- >=1.5.0 <2.0.9.2 · >=2.1.0.0 <2.1.4.2 · >=2.2.0.0 <2.2.6.2 · >=3.0.0.0 <3.0.4.1
- Fixed in
- 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1
Denial of service via multipart parsing in Rack
- Affected
- >=2.0.0 <2.0.9.2 · >=2.1.0.0 <2.1.4.2 · >=2.2.0.0 <2.2.6.1 · >=3.0.0.0 <3.0.4.1
- Fixed in
- 2.0.9.2, 2.1.4.2, 2.2.6.1, 3.0.4.1
Every rack 3.0.x release
Affected: 3.0.0 to 3.0.18. Latest rack: 3.2.8.
| Version | Known advisories |
|---|---|
| rack 3.0.18 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780 |
| rack 3.0.17 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780 |
| rack 3.0.16 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780 |
| rack 3.0.15 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727 |
| rack 3.0.14 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727 |
| rack 3.0.13 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610 |
| rack 3.0.12 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111 |
| rack 3.0.11 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184 |
| rack 3.0.10 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184 |
| rack 3.0.9.1 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184 |
| rack 3.0.9 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146 |
| rack 3.0.8 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146 |
| rack 3.0.7 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146 |
| rack 3.0.6.1 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146 |
| rack 3.0.6 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539 |
| rack 3.0.5 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539 |
| rack 3.0.4.2 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539 |
| rack 3.0.4.1 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530 |
| rack 3.0.4 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530, CVE-2022-44571, CVE-2022-44570, CVE-2022-44572 |
| rack 3.0.3 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530, CVE-2022-44571, CVE-2022-44570, CVE-2022-44572 |
| rack 3.0.2 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530, CVE-2022-44571, CVE-2022-44570, CVE-2022-44572 |
| rack 3.0.1 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530, CVE-2022-44571, CVE-2022-44570, CVE-2022-44572 |
| rack 3.0.0 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125109, CVE-2026-125110, CVE-2026-34835, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-32762, CVE-2026-26961, CVE-2026-34827, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-46727, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26141, CVE-2024-26146, CVE-2023-27539, CVE-2023-27530, CVE-2022-44571, CVE-2022-44570, CVE-2022-44572 |
Which of your client projects are still on rack 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact rack version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other rack versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.