CVE-2026-54297

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

June 19, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Uncontrolled recursion in NestedParamsEncoder allows stack exhaustion DoS via deeply nested query parameters · Advisory · lostisland/faraday · GitHub

https://github.com/lostisland/faraday/security/advisories/GHSA-98m9-hrrm-r99r

Vendor Advisories for CVE-2026-54297(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-faraday-0:1.10.6-1.el9sat2026-08-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-faraday1.1.0-6 ... 2.7.1-2 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-faraday1.1.0-7 ... 2.7.1-2 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-faraday2.12.2-1, 2.14.0-1, 2.14.1-1, 2.14.3-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-faraday2.12.2-1, 2.14.0-1, 2.14.1-12.14.3-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
faraday1.0.0 ... 1.9.3 (27 versions)1.10.6—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 87× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 02:42 UTCEG score recompute
  4. 2026-08-25 02:42 UTCVendor advisory
  5. 2026-08-24 14:00 UTCEG score recompute
  6. 2026-08-24 14:00 UTCVendor advisory
  7. 2026-08-24 01:09 UTCVendor advisory
  8. 2026-08-23 12:25 UTCEG score recompute
  9. 2026-08-23 12:25 UTCVendor advisory
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 23:42 UTCEG score recompute
  12. 2026-08-22 23:42 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 22:23 UTCVendor advisory
  15. 2026-08-21 09:26 UTCEG score recompute
  16. 2026-08-21 09:26 UTCVendor advisory
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 20:43 UTCVendor advisory
  19. 2026-08-20 08:00 UTCEG score recompute
  20. 2026-08-20 08:00 UTCVendor advisory
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-19 07:02 UTCEG score recompute
  23. 2026-08-19 07:02 UTCVendor advisory
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 04:59 UTCVendor advisory
  2. 2026-08-16 16:16 UTCEG score recompute
  3. 2026-08-16 16:16 UTCVendor advisory
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 03:33 UTCEG score recompute
  6. 2026-08-16 03:33 UTCVendor advisory
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 14:51 UTCVendor advisory
  9. 2026-08-15 02:08 UTCEG score recompute
  10. 2026-08-15 02:08 UTCVendor advisory
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 13:26 UTCEG score recompute
  13. 2026-08-14 13:26 UTCVendor advisory
  14. 2026-08-14 12:29 UTCEG score recompute
  15. 2026-08-14 12:29 UTCVendor advisory
  16. 2026-08-14 01:02 UTCEG score recompute
  17. 2026-08-14 01:02 UTCVendor advisory
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 12:19 UTCVendor advisory
  20. 2026-08-12 23:37 UTCEG score recompute
  21. 2026-08-12 23:37 UTCVendor advisory
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 10:55 UTCVendor advisory
  24. 2026-08-11 22:12 UTCEG score recompute
  25. 2026-08-11 22:12 UTCVendor advisory
  26. 2026-08-11 09:27 UTCVendor advisory
  27. 2026-08-10 20:45 UTCVendor advisory
  28. 2026-08-10 08:03 UTCVendor advisory
  29. 2026-08-09 19:21 UTCEG score recompute
  30. 2026-08-09 19:21 UTCVendor advisory
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 06:39 UTCVendor advisory
  33. 2026-08-08 17:57 UTCVendor advisory
  34. 2026-08-08 05:14 UTCVendor advisory
  35. 2026-08-07 16:32 UTCEG score recompute
  36. 2026-08-07 16:32 UTCVendor advisory
  37. 2026-08-07 03:50 UTCVendor advisory
  38. 2026-08-06 15:08 UTCEG score recompute
  39. 2026-08-06 15:08 UTCVendor advisory
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-06 02:20 UTCEG score recompute
  42. 2026-08-06 02:20 UTCVendor advisory
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-05 13:38 UTCEG score recompute
  45. 2026-08-05 13:38 UTCVendor advisory
  46. 2026-08-05 12:31 UTCVendor advisory
  47. 2026-08-04 15:19 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 20:47 UTCEG score recompute
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 06:29 UTCEG score recompute
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 05:02 UTCEG score recompute
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 22:19 UTCEG score recompute
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 03:01 UTCEG score recompute
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-29 01:35 UTCEG score recompute
  61. 2026-07-28 15:37 UTCEPSS rescore
  62. 2026-07-27 21:20 UTCEG score recompute
  63. 2026-07-26 16:49 UTCEG score recompute
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:18 UTCEPSS rescore
  67. 2026-07-23 03:19 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescore
  69. 2026-07-21 15:25 UTCEPSS rescore
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 02:29 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-16 17:03 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-54297?
CVE-2026-54297 is a high vulnerability published on June 19, 2026. 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…
When was CVE-2026-54297 disclosed?
CVE-2026-54297 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54297 actively exploited?
CVE-2026-54297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54297?
CVE-2026-54297 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54297?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54297, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54297

Explore →

Is Your Infrastructure Affected by CVE-2026-54297?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs