{"answers":{"affected":"2 open source packages ship an affected version, including rack. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59830 in the wild and no public exploit code.","fix":"Upgrade rack to 2.2.18 or later.","what":"CVE-2025-59830 is a high-severity denial of service vulnerability in rack, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59830 and fix it if it is affected.\n\nWhat it is: CVE-2025-59830 is a high-severity denial of service vulnerability in rack, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59830 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rack (RubyGems): affected all versions; fixed in 2.2.18\n- rack (RubyGems): affected all versions; fixed in 2.2.18\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59830/ (Markdown: https://insights.sbomify.com/CVE-2025-59830/index.md)","id":"CVE-2025-59830","markdown":"https://insights.sbomify.com/CVE-2025-59830/index.md","name":"CVE-2025-59830","record":{"aliases":["DEBIAN-CVE-2025-59830","GHSA-625h-95r8-8xpm","MINI-g4w3-gvr3-h232","MINI-h6mq-42gm-4qhr","MINI-jcj8-ph3h-wxv8","MINI-p8fx-9m2q-qhr9","MINI-wr88-5f8m-8fhq","UBUNTU-CVE-2025-59830","USN-7784-1","openSUSE-SU-2025:15587-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby web server interface","requires_auth":"none","summary":"Attackers can bypass parameter limits in Rack QueryParser using semicolon separators, causing resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rack","vendor":"rack"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by \u0026, while still splitting on both \u0026 and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.","ecosystems":["RubyGems","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters","id":"CVE-2025-59830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"`git-comiters` Command Injection vulnerability","id":"CVE-2025-59831"},"packages":[{"ecosystem":"RubyGems","fixed":["2.2.18"],"introduced":["0"],"last_affected":[],"package":"rack","purl":null,"source":"GHSA-625h-95r8-8xpm"},{"ecosystem":"RubyGems","fixed":["2.2.18"],"introduced":["0"],"last_affected":[],"package":"rack","purl":"pkg:gem/rack","source":"GHSA-625h-95r8-8xpm"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.2.18-1.1"],"introduced":["0"],"last_affected":[],"package":"rubygem-rack-2.2","purl":"pkg:rpm/opensuse/rubygem-rack-2.2\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15587-1"}],"prev":{"headline":"Claude Code: Permission deny bypass is possible through symlink","id":"CVE-2025-59829"},"products":["rack"],"published":"2025-09-25","related":[{"cvss_score":7.5,"headline":"Rack: Local file inclusion in `Rack::Static` via URL Prefix Matching","id":"CVE-2026-34785","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.5,"headline":"Rack: Algorithmic-Complexity DoS in Rack::Multipart::Parser","id":"CVE-2026-34827","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.5,"headline":"Rack: Denial of Service via Unbounded Multipart File Upload Without Content-Length","id":"CVE-2026-34829","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.5,"headline":"Rack has a Directory Traversal via Rack:Directory","id":"CVE-2026-22860","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":7.5,"headline":"Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing","id":"CVE-2025-61919","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":7.5,"headline":"Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)","id":"CVE-2025-61770","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":7.5,"headline":"Rack's multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)","id":"CVE-2025-61771","kev_date_added":null,"published":"2025-10-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-25","vendors":["rack"]},"summary":"Attackers can bypass parameter limits in Rack QueryParser using semicolon separators, causing resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2025-59830/"}