CVE-2026-26961: Rack: Multipart Boundary Parsing Ambiguity allowing WAF Bypass
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: ruby-rack (Debian:12) 2.2.22-0+deb12u2; ruby-rack (Debian:13) 3.1.20-0+deb13u2; ruby-rack (Debian:14) 3.2.6-2.
Low priority for now. Upgrade to ruby-rack (Debian:12) 2.2.22-0+deb12u2; ruby-rack (Debian:13) 3.1.20-0+deb13u2; ruby-rack (Debian:14) 3.2.6-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Multipart::Parser extracts the boundary parameter from multipart/form-data using a greedy regular expression. When a Content-Type header contains multiple boundary parameters, Rack selects the last one rather than the first. In deployments where an upstream proxy, WAF, or intermediary interprets the first boundary parameter, this mismatch can allow an attacker to smuggle multipart content past upstream inspection and have Rack parse a different body structure than the intermediary validated. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.
- Published
- Apr 2, 2026
- Updated
- Jul 24, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-436
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · GitHub_M
- 3.7
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rack | rack | cpe:2.3:a:rack:rack |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
rack rack
- < 2.2.23, >= 3.0.0.beta1, < 3.1.21, >= 3.2.0, < 3.2.6affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rack rackbefore 2.2.23
- rack rack3.0.0 and later · before 3.1.21
- rack rack3.2.0 and later · before 3.2.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | ruby-rack | before 2.2.22-0+deb12u2 | 2.2.22-0+deb12u2 |
| Debian:13 | ruby-rack | before 3.1.20-0+deb13u2 | 3.1.20-0+deb13u2 |
| Debian:14 | ruby-rack | before 3.2.6-2 | 3.2.6-2 |
| openSUSE:Leap 16.0 | rmt-server | before 3.1.0-160000.1.1 | 3.1.0-160000.1.1 |
| openSUSE:Tumbleweed | rubygem-rack | before 3.2.8-1.1 | 3.2.8-1.1 |
| openSUSE:Tumbleweed | rubygem-rack-2.2 | before 2.2.23-1.1 | 2.2.23-1.1 |
| RubyGems | rack | from 3.0.0.beta1 · before 3.1.21 | 3.1.21 |
| RubyGems | rack | from 3.2.0 · before 3.2.6 | 3.2.6 |
| RubyGems | rack | before 2.2.23 | 2.2.23 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | rmt-server | before 2.27-150500.3.47.1 | 2.27-150500.3.47.1 |
| SUSE:Linux Enterprise Server 16.0 | rmt-server | before 3.1.0-160000.1.1 | 3.1.0-160000.1.1 |
Same product
rack: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-25126Rack ReDos in content type parsing (2nd degree polynomial)41Plan
- CVE-2024-26146Possible Denial of Service Vulnerability in Rack Header Parsing31Monitor
- CVE-2023-27530A DoS vulnerability exists in Rack <v3.0.4.2, <v2.2.6.3, <v2.1.4.3 and <v2.0.9.3 within in the Multipart MIME parsing code in which could…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-22860Feb 18, 2026 · Rack has a Directory Traversal via Rack:Directory30Monitor
- ← EarlierCVE-2026-25500Feb 18, 2026 · Rack's Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href21Monitor
- Later →CVE-2026-34230Apr 2, 2026 · Rack: Quadratic complexity in Rack::Utils.select_best_encoding via wildcard Accept-Encoding header30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:ruby-rack | 2.2.22-0+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:rmt-server | 3.1.0-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:rubygem-rack | 3.2.8-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rubygem-rack-2.2 | 2.2.23-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| RubyGems:rack | 2.2.23 | Package registry (OSV) |
| RubyGems:rack | 3.1.21 | Package registry (OSV) |
| RubyGems:rack | 3.2.6 | Package registry (OSV) |
| suse:rmt-server | 3.1.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-327620 days apartRack: Forwarded Header semicolon injection enables Host and Scheme spoofing26Monitor
- CVE-2026-125108221 days apartRack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass14Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-436 · Interpretation ConflictCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.