Is rack 1.2 vulnerable?
RubyGems · 9 releases from 1.2.0 to 1.2.8 · latest rack is 3.2.8 · checked 18 Nov 2026
Yes: 34 known advisories
Yes. rack 1.2.8, the last 1.2 release, is affected by 34 known security advisories (1 critical, 16 high, 15 medium, 2 low), including CVE-2022-30123, CVE-2026-125111, CVE-2026-34829. 4 more affect earlier 1.2.x releases. Upgrade to 2.2.25 or later to fix all of them.
bundle update --conservative rack # Gemfile: '>= 2.2.25'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 1.2.8
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::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 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'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 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
Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)
- Affected
- <2.2.19 · >=3.1 <3.1.17 · >=3.2 <3.2.2
- Fixed in
- 2.2.19, 3.1.17, 3.2.2
Rack: Multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)
- Affected
- <2.2.19 · >=3.1 <3.1.17 · >=3.2 <3.2.2
- Fixed in
- 2.2.19, 3.1.17, 3.2.2
Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
- Affected
- <2.2.19 · >=3.1 <3.1.17 · >=3.2 <3.2.2
- Fixed in
- 2.2.19, 3.1.17, 3.2.2
Rack has an unsafe default in Rack::QueryParser allows params_limit bypass via semicolon-separated parameters
- Affected
- <2.2.18
- Fixed in
- 2.2.18
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
Rack session gets restored after deletion
- Affected
- <2.2.14
- Fixed in
- 2.2.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 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
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 Multipart Parsing
- Affected
- >=1.2 <2.0.9.1 · >=2.1 <2.1.4.1 · >=2.2 <2.2.3.1
- Fixed in
- 2.0.9.1, 2.1.4.1, 2.2.3.1
Possible shell escape sequence injection vulnerability in Rack
- Affected
- <2.0.9.1 · >=2.1 <2.1.4.1 · >=2.2 <2.2.3.1
- Fixed in
- 2.0.9.1, 2.1.4.1, 2.2.3.1
Directory traversal in Rack::Directory app bundled with Rack
- Affected
- <2.1.3
- Fixed in
- 2.1.3
Rack allows Percent-encoded cookies to overwrite existing prefixed cookie names
- Affected
- <2.1.4 · >=2.2.0 <2.2.3
- Fixed in
- 2.1.4, 2.2.3
Possible Information Leak / Session Hijack Vulnerability in Rack
- Affected
- <1.6.12 · >=2.0.0 <2.0.8
- Fixed in
- 1.6.12, 2.0.8
Rack vulnerable to Cross-site Scripting
- Affected
- >=2.0.0 <2.0.6 · <1.6.11
- Fixed in
- 1.6.11, 2.0.6
Fixed within 1.2.x, affecting earlier releases
Rack Gem Subject to Denial of Service via Hash Collisions
- Affected
- <1.1.3 · >=1.2.0 <1.2.5 · >=1.3.0 <1.3.6
- Fixed in
- 1.1.3, 1.2.5, 1.3.6
Rack arbitrary code execution via timing attack
- Affected
- >=1.5.0 <1.5.2 · >=1.4.0 <1.4.5 · >=1.3.0 <1.3.10 · >=1.2.0 <1.2.8 · >=1.1.0 <1.1.6
- Fixed in
- 1.1.6, 1.2.8, 1.3.10, 1.4.5, 1.5.2
Rack vulnerable to Denial of Service
- Affected
- >=1.1.0 <1.1.5 · >=1.2.0 <1.2.7 · >=1.3.0 <1.3.9 · >=1.4.0 <1.4.4
- Fixed in
- 1.1.5, 1.2.7, 1.3.9, 1.4.4
Rack vulnerable to REDoS
- Affected
- <1.1.4 · >=1.2.0 <1.2.6 · >=1.3.0 <1.3.7 · >=1.4.0 <1.4.2
- Fixed in
- 1.1.4, 1.2.6, 1.3.7, 1.4.2
Every rack 1.2.x release
Affected: 1.2.0 to 1.2.8. Latest rack: 3.2.8.
| Version | Known advisories |
|---|---|
| rack 1.2.8 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471 |
| rack 1.2.7 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2013-0263, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471 |
| rack 1.2.6 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471 |
| rack 1.2.5 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
| rack 1.2.4 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2011-5036, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
| rack 1.2.3 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2011-5036, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
| rack 1.2.2 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2011-5036, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
| rack 1.2.1 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2011-5036, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
| rack 1.2.0 | CVE-2026-125111, CVE-2026-125108, CVE-2026-125110, CVE-2026-34831, CVE-2026-34830, CVE-2026-34829, CVE-2026-34763, CVE-2026-34230, CVE-2026-26961, CVE-2026-34826, CVE-2026-34786, CVE-2026-34785, CVE-2026-25500, CVE-2026-22860, CVE-2025-61919, CVE-2025-61780, CVE-2025-61772, CVE-2025-61771, CVE-2025-61770, CVE-2025-59830, CVE-2025-46727, CVE-2025-32441, CVE-2025-27610, CVE-2025-27111, CVE-2025-25184, CVE-2024-25126, CVE-2024-26146, CVE-2023-27530, CVE-2022-30122, CVE-2022-30123, CVE-2011-5036, CVE-2013-0263, CVE-2013-0184, CVE-2020-8161, CVE-2020-8184, CVE-2019-16782, CVE-2018-16471, CVE-2012-6109 |
Which of your client projects are still on rack 1.2?
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.