CVE-2026-125108
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
CVE-2026-125108 is a low vulnerability (CVSS 3.7) in Rack, published November 9, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.24%, the 15th percentile. Fixed in rack 2.2.25.
- Severity
- 3.7 LowCVSS 3.1, CVE List
- Exploit chance
- 0.24%EPSS, 15th percentile
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
2.2.25rack +21 more
Description
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
rackRubyGems | before 2.2.25 | 2.2.25 |
rackRubyGems | 3.0.0 up to 3.1.23 | 3.1.23 |
rackRubyGems | 3.2.0 up to 3.2.8 | 3.2.8 |
ruby-rackDebian:12 | All versions, plus listed versions 2.2.13-1~deb12u12.2.20-0+deb12u12.2.22-0+deb12u12.2.22-0+deb12u22.2.6.4-1 Show 23 moreShow less2.2.6.4-1+deb12u12.2.7-12.2.7-1.13.0.0-13.0.8-13.0.8-23.0.8-33.0.8-43.1.12-13.1.12-2~exp13.1.16-0.13.1.18-13.1.18-1~deb13u13.1.9-1~exp13.1.9-23.2.4-13.2.5-13.2.5-23.2.6-13.2.6-23.2.6-33.2.7-13.2.8-1 | None known |
ruby-rackDebian:13 | All versions, plus listed versions 3.1.16-0.13.1.18-13.1.18-1~deb13u13.1.20-0+deb13u13.1.20-0+deb13u2 Show 8 moreShow less3.2.4-13.2.5-13.2.5-23.2.6-13.2.6-23.2.6-33.2.7-13.2.8-1 | None known |
ruby-rackDebian:14 | before 3.2.8-1, plus listed versions 3.1.16-0.13.1.18-13.1.18-1~deb13u13.2.4-13.2.5-1 Show 5 moreShow less3.2.5-23.2.6-13.2.6-23.2.6-33.2.7-1 | 3.2.8-1 |
gitlab-rails-18Docker Hardened Images:Alpine:3.24 | Listed versions 18.11.11-r018.11.11-r118.11.11-r218.11.12-r018.11.12-r1 Show 15 moreShow less18.11.12-r218.11.12-r318.11.12-r418.11.14-r018.11.14-r118.11.14-r1018.11.14-r1118.11.14-r218.11.14-r318.11.14-r418.11.14-r518.11.14-r618.11.14-r718.11.14-r818.11.14-r9 | None known |
gitlab-rails-19Docker Hardened Images:Alpine:3.24 | Listed versions 19.1.8-r019.1.8-r119.4.1-r019.4.1-r119.4.1-r2 Show 16 moreShow less19.4.1-r319.4.2-r019.5.3-r019.5.3-r119.5.3-r219.5.3-r319.5.3-r419.5.3-r519.5.3-r619.5.3-r719.5.3-r819.5.4-r019.5.4-r119.5.5-r019.5.5-r119.5.5-r2 | None known |
gitlab-exporterDocker Hardened Images:Debian:13 | Listed versions 16.10.0-116.10.0-1016.10.0-1116.10.0-1216.10.0-13 Show 45 moreShow less16.10.0-1416.10.0-1516.10.0-1616.10.0-1716.10.0-1816.10.0-1916.10.0-216.10.0-2016.10.0-2116.10.0-2216.10.0-2316.10.0-2416.10.0-2516.10.0-2616.10.0-2716.10.0-2816.10.0-2916.10.0-316.10.0-3016.10.0-3116.10.0-3216.10.0-3316.10.0-3416.10.0-3516.10.0-3616.10.0-3716.10.0-3816.10.0-3916.10.0-416.10.0-4016.10.0-4116.10.0-4216.10.0-4316.10.0-4416.10.0-4516.10.0-4616.10.0-4716.10.0-4816.10.0-4916.10.0-516.10.0-5016.10.0-5116.10.0-616.10.0-716.10.0-8 | None known |
gitlab-rails-18Docker Hardened Images:Debian:13 | Listed versions 18.11.11-018.11.11-118.11.11-218.11.12-018.11.12-1 Show 18 moreShow less18.11.12-218.11.14-018.11.14-118.11.14-1018.11.14-1118.11.14-1218.11.14-1318.11.14-1418.11.14-1518.11.14-1618.11.14-218.11.14-318.11.14-418.11.14-518.11.14-618.11.14-718.11.14-818.11.14-9 | None known |
Show 12 moreShow less
| Package | Affected | Fixed |
|---|---|---|
gitlab-rails-19Docker Hardened Images:Debian:13 | Listed versions 19.1.8-019.1.8-119.4.1-019.4.1-119.4.1-2 Show 20 moreShow less19.4.2-019.5.3-019.5.3-119.5.3-219.5.3-319.5.3-419.5.3-519.5.3-619.5.3-719.5.3-819.5.3-919.5.4-019.5.4-119.5.5-019.5.5-119.5.5-219.5.5-319.5.5-419.5.5-519.5.5-6 | None known |
rackRubyGems | before 2.2.25, plus listed versions 0.1.00.2.00.3.00.4.00.9.0 Show 45 moreShow less0.9.11.0.01.0.11.1.01.1.11.1.1.pre1.1.21.1.31.1.41.1.51.1.61.2.01.2.11.2.21.2.31.2.41.2.51.2.61.2.71.2.81.3.01.3.0.beta1.3.0.beta21.3.11.3.101.3.21.3.31.3.41.3.51.3.61.3.71.3.81.3.91.4.01.4.11.4.21.4.31.4.41.4.51.4.61.4.71.5.01.5.0.beta.11.5.0.beta.21.5.1 | 2.2.25 |
rackRubyGems | 3.0.0 up to 3.1.23, plus listed versions 3.0.13.0.103.0.113.0.123.0.13 Show 40 moreShow less3.0.143.0.153.0.163.0.173.0.183.0.23.0.33.0.43.0.4.13.0.4.23.0.53.0.63.0.6.13.0.73.0.83.0.93.0.9.13.1.03.1.13.1.103.1.113.1.123.1.133.1.143.1.153.1.163.1.173.1.183.1.193.1.23.1.203.1.213.1.223.1.33.1.43.1.53.1.63.1.73.1.83.1.9 | 3.1.23 |
rackRubyGems | 3.2.0 up to 3.2.8, plus listed versions 3.2.13.2.23.2.33.2.43.2.53.2.63.2.7 | 3.2.8 |
ruby-rackUbuntu:Pro:14.04:LTS | All versions, plus listed versions 1.5.2-11.5.2-1ubuntu0.1~esm11.5.2-3+deb8u3ubuntu1~esm21.5.2-3+deb8u3ubuntu1~esm31.5.2-3+deb8u3ubuntu1~esm4 Show 6 moreShow less1.5.2-3+deb8u3ubuntu1~esm61.5.2-3+deb8u3ubuntu1~esm71.5.2-3+deb8u3ubuntu1~esm81.5.2-3+deb8u3ubuntu1~esm91.5.2-3+deb8u3ubuntu1~esm101.5.2-3+deb8u3ubuntu1~esm11 | None known |
ruby-rackUbuntu:Pro:16.04:LTS | All versions, plus listed versions 1.5.2-41.6.4-21.6.4-31.6.4-3ubuntu0.11.6.4-3ubuntu0.2 Show 9 moreShow less1.6.4-3ubuntu0.2+esm11.6.4-3ubuntu0.2+esm21.6.4-3ubuntu0.2+esm41.6.4-3ubuntu0.2+esm51.6.4-3ubuntu0.2+esm61.6.4-3ubuntu0.2+esm71.6.4-3ubuntu0.2+esm81.6.4-3ubuntu0.2+esm91.6.4-3ubuntu0.2+esm10 | None known |
ruby-rackUbuntu:Pro:18.04:LTS | All versions, plus listed versions 1.6.4-41.6.4-4ubuntu0.11.6.4-4ubuntu0.21.6.4-4ubuntu0.2+esm11.6.4-4ubuntu0.2+esm2 Show 7 moreShow less1.6.4-4ubuntu0.2+esm41.6.4-4ubuntu0.2+esm51.6.4-4ubuntu0.2+esm61.6.4-4ubuntu0.2+esm71.6.4-4ubuntu0.2+esm81.6.4-4ubuntu0.2+esm91.6.4-4ubuntu0.2+esm10 | None known |
ruby-rackUbuntu:Pro:20.04:LTS | All versions, plus listed versions 2.0.6-32.0.7-22.0.7-2ubuntu0.12.0.7-2ubuntu0.1+esm12.0.7-2ubuntu0.1+esm2 Show 8 moreShow less2.0.7-2ubuntu0.1+esm32.0.7-2ubuntu0.1+esm42.0.7-2ubuntu0.1+esm52.0.7-2ubuntu0.1+esm62.0.7-2ubuntu0.1+esm72.0.7-2ubuntu0.1+esm82.0.7-2ubuntu0.1+esm92.0.7-2ubuntu0.1+esm10 | None known |
ruby-rackUbuntu:Pro:22.04:LTS | All versions, plus listed versions 2.1.4-32.1.4-42.1.4-52.1.4-5ubuntu12.1.4-5ubuntu1+esm2 Show 10 moreShow less2.1.4-5ubuntu1+esm32.1.4-5ubuntu1+esm42.1.4-5ubuntu1+esm52.1.4-5ubuntu1.12.1.4-5ubuntu1.1+esm12.1.4-5ubuntu1.1+esm22.1.4-5ubuntu1.22.1.4-5ubuntu1.2+esm12.1.4-5ubuntu1.2+esm22.1.4-5ubuntu1.2+esm3 | None known |
ruby-rackUbuntu:24.04:LTS | All versions, plus listed versions 2.2.4-32.2.7-12.2.7-1ubuntu0.12.2.7-1ubuntu0.22.2.7-1ubuntu0.3 Show 4 moreShow less2.2.7-1ubuntu0.42.2.7-1ubuntu0.52.2.7-1ubuntu0.62.2.7-1ubuntu0.7 | None known |
ruby-rackUbuntu:26.10 | All versions, plus listed versions 3.2.4-1ubuntu13.2.6-3 | None known |
ruby-rackUbuntu:26.04:LTS | All versions, plus listed versions 3.1.16-0.13.1.18-13.1.18-1build13.2.4-1ubuntu13.2.4-1ubuntu1.1 | None known |
What each source reports
CVE List Score used 3.7
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
CVE-2026-125108- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-436
- Updated
- 2026-11-09
EUVDEUVD-2026-120481 3.7
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
EUVD-2026-120481- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-13
GitHub AdvisoriesGHSA-p8x9-v4hv-2w4g 3.7
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
Summary
The guard added for CVE-2026-26961 (GHSA-vgpv-f759-9wx3), which rejects multipart requests with more than one boundary parameter, only inspects the part of the Content-Type header after the boundary it extracts. A Content-Type whose first boundary parameter is empty or begins with a quote, semicolon, or comma is skipped by the extraction pattern, so a second boundary parameter is accepted silently and Rack parses the body with a boundary that a conforming parser would not derive from the header.
Details
Rack::Multipart::Parser.parse_boundary extracts the boundary with a regular expression that uses a lazy prefix and a value class excluding ", ;, and ,. For a header such as multipart/form-data; boundary=";boundary=AaB03x" or multipart/form-data; boundary=; boundary=AaB03x, the pattern skips the first boundary= and anchors on the second, and the subsequent check for another boundary= in the remaining text finds nothing. Rack then uses AaB03x.
RFC 9110 parses the first header as a single parameter whose value is ;boundary=AaB03x, which is not a legal boundary under RFC 2046, so the only conformant outcome is rejection. Inspecting intermediaries that implement the standard grammar, such as ModSecurity, see a different boundary or no multipart body at all.
The fix counts boundary= occurrences across the entire header value and rejects the request when there is more than one.
Impact
As with CVE-2026-26961, an attacker can craft a multipart request that a web application firewall or other inspecting proxy in front of a Rack application interprets differently from Rack, so form fields and file uploads reach the application without inspection. Rack itself grants no capability beyond that of a well-formed request with the same body. All supported versions, including 2.2, are affected.
Mitigation
- Update to a patched version of Rack.
- Reject requests whose
Content-Typecontains more than oneboundaryparameter at the reverse proxy.
- Record
GHSA-p8x9-v4hv-2w4g- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-436
- Updated
- 2026-11-10
NVD 3.7
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
CVE-2026-125108- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-436
- Updated
- 2026-11-09
OSV 3.7
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
CVE-2026-125108- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-436
- Updated
- 2026-11-11
OSVDEBIAN-CVE-2026-125108 3.7
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
DEBIAN-CVE-2026-125108- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-10
OSVDHI-ahkp-y56b-dqdg-eyle 3.7
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary…
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
DHI-ahkp-y56b-dqdg-eyle- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-16
OSVGHSA-p8x9-v4hv-2w4g 3.7
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
Summary
The guard added for CVE-2026-26961 (GHSA-vgpv-f759-9wx3), which rejects multipart requests with more than one boundary parameter, only inspects the part of the Content-Type header after the boundary it extracts. A Content-Type whose first boundary parameter is empty or begins with a quote, semicolon, or comma is skipped by the extraction pattern, so a second boundary parameter is accepted silently and Rack parses the body with a boundary that a conforming parser would not derive from the header.
Details
Rack::Multipart::Parser.parse_boundary extracts the boundary with a regular expression that uses a lazy prefix and a value class excluding ", ;, and ,. For a header such as multipart/form-data; boundary=";boundary=AaB03x" or multipart/form-data; boundary=; boundary=AaB03x, the pattern skips the first boundary= and anchors on the second, and the subsequent check for another boundary= in the remaining text finds nothing. Rack then uses AaB03x.
RFC 9110 parses the first header as a single parameter whose value is ;boundary=AaB03x, which is not a legal boundary under RFC 2046, so the only conformant outcome is rejection. Inspecting intermediaries that implement the standard grammar, such as ModSecurity, see a different boundary or no multipart body at all.
The fix counts boundary= occurrences across the entire header value and rejects the request when there is more than one.
Impact
As with CVE-2026-26961, an attacker can craft a multipart request that a web application firewall or other inspecting proxy in front of a Rack application interprets differently from Rack, so form fields and file uploads reach the application without inspection. Rack itself grants no capability beyond that of a well-formed request with the same body. All supported versions, including 2.2, are affected.
Mitigation
- Update to a patched version of Rack.
- Reject requests whose
Content-Typecontains more than oneboundaryparameter at the reverse proxy.
- Record
GHSA-p8x9-v4hv-2w4g- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-436
- Updated
- 2026-11-10
OSVUBUNTU-CVE-2026-125108 3.7
Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.
- Record
UBUNTU-CVE-2026-125108- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-13
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| published | EUVD | |
| affected, aliases, references | OSV | |
| published | EUVD | |
| affected, references | OSV | |
| affected, references | GitHub Advisories | |
| affected, aliases, facts, references | OSV | |
| aliases, references | OSV | |
| aliases, published | EUVD, NVD | |
| first indexed | CVE List |
Dates are when Every CVE recorded each change. Upstream dates may differ.
References
github.com/rack/rack/security/advisories/GHSA-p8x9-v4hv-2w4g
github.com/rack/rack/commit/19a1a19cb4da97d61c8d5effeb2e927c44370ae9
github.com/rack/rack/commit/a29512324265790a5536b830490075d0d79323be
github.com/rack/rack/commit/d5e928b803da30b8e40171dbd4be39bed7daa6fa
github.com/rack/rack/releases/tag/v2.2.25
github.com/rack/rack/releases/tag/v3.1.23
Show 12 moreShow less
github.com/rack/rack/releases/tag/v3.2.8
nvd.nist.gov/vuln/detail/CVE-2026-125108
github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/GHSA-p8x9-v4hv-2w4g.yml
github.com/advisories/GHSA-p8x9-v4hv-2w4g
github.com/CVEProject/cvelistV5/tree/main/cves/2026/125xxx/CVE-2026-125108.json
security-tracker.debian.org/tracker/CVE-2026-125108
scout.docker.com/v/DHI-ahkp-y56b-dqdg-eyle
access.redhat.com/security/cve/CVE-2026-125108
cve.org/CVERecord?id=CVE-2026-125108
ubuntu.com/security/CVE-2026-125108
people.ubuntu.com/~ubuntu-security/cve/CVE-2026-125108
github.com/rack/rack
Left out here: 76 versions. The JSON record has them.