llamaCVEVulnerability Intelligence
/
Advisory · GitHub · RubyGems · rack

GHSA-VGPV-F759-9WX3

Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versionesPrimer parche a -1 d de la divulgación
Exposición231 dDesde la divulgación, 2 abr 2026, 3:30 p. m.
Detección228 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 2.2.23 +2
Monitoreo
Detectada
1 abr 26
2 abr 26
10 sept 26
17 nov 26
19 nov 26
1 abr 26
29 may 26
26 jul 26
22 sept 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 2.2.23 rack · -1 d desde divulgación
Remediación Parche 3.1.21 rack · -1 d desde divulgación
Remediación Parche 3.2.6 rack · -1 d desde divulgación
Divulgación Publicada GHSA-VGPV-F759-9WX3 divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

`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.

Details

Rack identifies the multipart boundary using logic equivalent to:

MULTIPART = %r|\Amultipart/.*boundary=\"?([^\";,]+)\"?|ni

Because the expression is greedy, it matches the last `boundary=` parameter in a header such as:

Content-Type: multipart/form-data; boundary=safe; boundary=malicious

As a result, Rack parses the request body using `malicious`, while another component may interpret the same header using `safe`.

This creates an interpretation conflict. If an upstream WAF or proxy inspects multipart parts using the first boundary and Rack later parses the body using the last boundary, a client may be able to place malicious form fields or uploaded content in parts that Rack accepts but the upstream component did not inspect as intended.

This issue is most relevant in layered deployments where security decisions are made before the request reaches Rack.

Impact

Applications that accept `multipart/form-data` uploads behind an inspecting proxy or WAF may be affected.

In such deployments, an attacker may be able to bypass upstream filtering of uploaded files or form fields by sending a request with multiple `boundary` parameters and relying on the intermediary and Rack to parse the request differently.

The practical impact depends on deployment architecture. If no upstream component relies on a different multipart interpretation, this behavior may not provide meaningful additional attacker capability.

Mitigation

  • Update to a patched version of Rack that rejects ambiguous multipart `Content-Type` headers or parses duplicate `boundary` parameters consistently.
  • Reject requests containing multiple `boundary` parameters.
  • Normalize or regenerate multipart metadata at the trusted edge before forwarding requests to Rack.
  • Avoid relying on upstream inspection of malformed multipart requests unless duplicate parameter handling is explicitly consistent across components.
Versiones

Rangos afectados

Afectada Corregida Última
rack< 2.2.23
rack≥ 3.0.0.beta1 < 3.1.21
rack≥ 3.2.0 < 3.2.6
2.2.23
3.0.0.beta1
3.1.21
3.2.0
3.2.6
3.2.8
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
rubygemsrack
Corregida 2.2.23, 3.1.21, 3.2.6 -1 d · -1 d · -1 d 3.2.8 no afectada
Versiones corregidas2.2.233.1.213.2.6
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-26961
Otrahttps://github.com/rack/rack/security/advisories/GHSA-vgpv-f759-9wx3
Otrahttps://github.com/rack/rack
Otrahttps://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2026-26961.yml

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.