CVE-2026-62864

Ring's nested-params middleware has inefficient regular expression complexity

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Ring is a Clojure web applications library inspired by Python's WSGI and Ruby's Rack. Prior to 1.15.5, `wrap-nested-params` in the `ring.middleware.nested-params` namespace uses a backtracking regular expression to match parameter names from URL query strings and HTTP request bodies. An attacker can craft a parameter name that drives quadratic O(n^2) matching work, causing regular-expression denial of service in applications using the middleware. `Ring-Defaults` users are also exposed because nested-params is enabled by default. Applications omitting the middleware do not expose this parsing path. This issue is fixed in version 1.15.5.

Analysis

AI-generated

Technical impact

Ring's wrap‑nested‑params middleware uses a backtracking regular expression to parse parameter names from URL query strings and request bodies. An attacker can supply a specially crafted parameter name that causes the regular expression to perform quadratic O(n^2) matching, leading to a denial‑of‑service that exhausts server resources. This vulnerability is a classic example of a regular‑expression denial of service (REGEXP-DSO).

Affected Systems

Ring library versions earlier than 1.15.5 are affected, including any application that uses the ring.middleware.nested‑params namespace. Applications built with Ring‑Defaults are also exposed because nested‑params is enabled by default. Omitting the middleware entirely avoids the vulnerable parsing path.

Risk and Exploitability

The CVSS score of 7.5 marks the issue as high severity. There is no EPSS score available, so the current exploitation probability is unknown, but the widespread use of HTTP query parameters and the remote nature of the attack vector suggest that the vulnerability could be abused when an attacker can send HTTP requests to the target application. The vulnerability is not listed in the CISA KEV catalog, indicating that no known widespread exploitation is documented at the time of analysis.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade ring to version 1.15.5 or later.
  • If an upgrade cannot be applied immediately, locate the use of wrap‑nested‑params in the application and remove or disable it, especially if nested parameters are not required.
  • Consider implementing input validation or whitelist constraints on parameter names to mitigate potential backtracking attacks if the middleware must remain enabled.

Generated by OpenCVE AI on October 30, 2026 at 23:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ring-clojure
Ring-clojure ring
Vendors & Products Ring-clojure
Ring-clojure ring
Type Values Removed Values Added
Description Ring is a Clojure web applications library inspired by Python's WSGI and Ruby's Rack. Prior to 1.15.5, `wrap-nested-params` in the `ring.middleware.nested-params` namespace uses a backtracking regular expression to match parameter names from URL query strings and HTTP request bodies. An attacker can craft a parameter name that drives quadratic O(n^2) matching work, causing regular-expression denial of service in applications using the middleware. `Ring-Defaults` users are also exposed because nested-params is enabled by default. Applications omitting the middleware do not expose this parsing path. This issue is fixed in version 1.15.5.
Title Ring's nested-params middleware has inefficient regular expression complexity
Weaknesses CWE-1333
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-1333

    Inefficient Regular Expression Complexity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 3:05 PM
Reserved
Jul 14, 2026, 9:10 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 9:17 PM
Modified
Nov 2, 2026, 7:34 PM
Severity
Important
Public date
Oct 30, 2026, 8:34 PM