# CVE-2026-54297: Faraday: Uncontrolled recursion in NestedParamsEncoder allows stack exhaustion DoS via deeply nested query parameters

> Attackers can cause denial of service in applications using Faraday by sending deeply nested query parameters that trigger stack exhaustion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 14 Aug 2026
- **Also known as:** CLEANSTART-2026-PK35326, CLEANSTART-2026-RL29531, DEBIAN-CVE-2026-54297, GHSA-98m9-hrrm-r99r, MINI-4prx-j44m-f64h, MINI-62j7-9jvc-j447, MINI-66j6-v3jc-j339, MINI-6prq-xm36-fxgj, MINI-6wx5-7gpf-7j4j, MINI-73v6-g65m-vqhx, MINI-8mx6-62m4-r7j2, MINI-92h5-9xvj-7j3h, MINI-95pp-698v-f9q5, MINI-c73h-3mq3-7hrh, MINI-ccr3-78h2-phqx, MINI-cw9j-f7jh-gmpj, MINI-cx8w-82m4-qgf3, MINI-frg3-2vx9-mf7j, MINI-gxxx-25pg-wcqc, MINI-h4x6-44h5-xmx2, MINI-hfxv-78rm-rmq7, MINI-hgvw-35fq-fx68, MINI-hjc7-62jp-q9cw, MINI-hx3f-g356-fpg6, MINI-mf3p-2m5v-r87g, MINI-pc85-2686-q6hv, MINI-pg37-m2f8-8m4c, MINI-ph6c-q693-j353, MINI-pqhx-h9c8-997v, MINI-w3m8-pwc2-26cm, MINI-wj5c-7656-vx63, UBUNTU-CVE-2026-54297

## What is CVE-2026-54297?

CVE-2026-54297 is a high-severity denial of service vulnerability in lostisland faraday, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters. From 1.0.0 until 1.10.6 and 2.14.3, Faraday::NestedParamsEncoder, the default nested query parameter encoder/decoder in Faraday, decodes nested query strings without enforcing a maximum nesting depth. A crafted query string causes Faraday to build a deeply nested Ruby Hash structure. The internal dehash routine then recursively walks this attacker-controlled structure without a depth limit. At sufficient depth, Ruby raises an uncaught SystemStackError (stack level too deep), crashing the calling thread or worker. This can lead to denial of service in applications that pass attacker-controlled query strings to Faraday's nested query parsing or URL-building paths. This vulnerability is fixed in 1.10.6 and 2.14.3.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-54297?

4 open source packages ship an affected version, including faraday. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `faraday` | RubyGems | From 1.0.0 | 1.10.6 |
| `faraday` | RubyGems | From 1.0.0 | 1.10.6 |
| `faraday` | RubyGems | From 2.0.0 | 2.14.3 |
| `faraday` | RubyGems | From 2.0.0 | 2.14.3 |

Products: Faraday Project Faraday.

## How do I fix CVE-2026-54297?

Upgrade faraday to a fixed version for your release line: 1.10.6 or 2.14.3.

## Is CVE-2026-54297 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54297 exists.

## Other vulnerabilities in lostisland faraday

- [CVE-2026-25765](https://insights.sbomify.com/CVE-2026-25765/): Faraday affected by SSRF via protocol-relative URL host override in build_exclusive_url (medium 5.8)
- [CVE-2026-33637](https://insights.sbomify.com/CVE-2026-33637/): Faraday: Protocol-relative URI objects still bypass host scoping (possible incomplete fix for GHSA-33mh-2634-fwr2) (not scored)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54297 and fix it if it is affected.

What it is: CVE-2026-54297 is a high-severity denial of service vulnerability in lostisland faraday, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54297 exists.

Affected packages and fixed versions:
- faraday (RubyGems): affected from 1.0.0; fixed in 1.10.6
- faraday (RubyGems): affected from 1.0.0; fixed in 1.10.6
- faraday (RubyGems): affected from 2.0.0; fixed in 2.14.3
- faraday (RubyGems): affected from 2.0.0; fixed in 2.14.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54297/ (Markdown: https://insights.sbomify.com/CVE-2026-54297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54297
- OSV: https://osv.dev/vulnerability/CVE-2026-54297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54297/
Summaries are generated and may contain mistakes; the official description above is the record.