{"answers":{"affected":"6 open source packages ship an affected version, including rack. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-61780 in the wild and no public exploit code.","fix":"Upgrade rack to a fixed version for your release line: 2.2.20, 3.1.18 or 3.2.3.","what":"CVE-2025-61780 is a medium-severity vulnerability in rack, published on 10 Oct 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-61780 and fix it if it is affected.\n\nWhat it is: CVE-2025-61780 is a medium-severity vulnerability in rack, published on 10 Oct 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-61780 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rack (RubyGems): affected all versions; fixed in 2.2.20\n- rack (RubyGems): affected all versions; fixed in 2.2.20\n- rack (RubyGems): affected from 3.0; fixed in 3.1.18\n- rack (RubyGems): affected from 3.0; fixed in 3.1.18\n- rack (RubyGems): affected from 3.2; fixed in 3.2.3\n- rack (RubyGems): affected from 3.2; fixed in 3.2.3\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-61780/ (Markdown: https://insights.sbomify.com/CVE-2025-61780/index.md)","id":"CVE-2025-61780","markdown":"https://insights.sbomify.com/CVE-2025-61780/index.md","name":"CVE-2025-61780","record":{"aliases":["CLEANSTART-2026-HO19975","DEBIAN-CVE-2025-61780","GHSA-r657-rxjc-j557","MINI-29cw-v24q-q78p","MINI-2qvh-mwcf-7w25","MINI-4fh9-fgp7-9qhq","MINI-62p4-fjg7-cgc8","MINI-7pvr-qvr4-8v87","MINI-8h58-84f5-xp88","MINI-c76c-6vw7-9hr3","MINI-gf53-ch35-f3j5","MINI-mmh5-wr2c-jrff","MINI-qf6f-rq74-mjvw","MINI-qg6c-693g-w8pw","MINI-qj9w-cj9v-cq27","MINI-w2c2-6q82-q536","MINI-xjj4-mwpr-h2m3","UBUNTU-CVE-2025-61780"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby web server interface","requires_auth":"none","summary":"Attackers can bypass proxy access controls to access protected internal endpoints by crafting specific headers in Rack::Sendfile.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rack","vendor":"rack"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a \"redirect\" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.","ecosystems":["RubyGems"],"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 has Possible Information Disclosure Vulnerability","id":"CVE-2025-61780","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":6,"n_references":4,"next":{"headline":"GraphQL IDOR allows authenticated user to delete workspace content of other users","id":"CVE-2025-61781"},"packages":[{"ecosystem":"RubyGems","fixed":["2.2.20"],"introduced":["0"],"last_affected":[],"package":"rack","purl":null,"source":"GHSA-r657-rxjc-j557"},{"ecosystem":"RubyGems","fixed":["2.2.20"],"introduced":["0"],"last_affected":[],"package":"rack","purl":"pkg:gem/rack","source":"GHSA-r657-rxjc-j557"},{"ecosystem":"RubyGems","fixed":["3.1.18"],"introduced":["3.0"],"last_affected":[],"package":"rack","purl":null,"source":"GHSA-r657-rxjc-j557"},{"ecosystem":"RubyGems","fixed":["3.1.18"],"introduced":["3.0"],"last_affected":[],"package":"rack","purl":"pkg:gem/rack","source":"GHSA-r657-rxjc-j557"},{"ecosystem":"RubyGems","fixed":["3.2.3"],"introduced":["3.2"],"last_affected":[],"package":"rack","purl":null,"source":"GHSA-r657-rxjc-j557"},{"ecosystem":"RubyGems","fixed":["3.2.3"],"introduced":["3.2"],"last_affected":[],"package":"rack","purl":"pkg:gem/rack","source":"GHSA-r657-rxjc-j557"}],"prev":{"headline":"Trustee's attestation-policy endpoint is not protected by admin autentication","id":"CVE-2025-61779"},"products":["rack"],"published":"2025-10-10","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":"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-10-10","vendors":["rack"]},"summary":"Attackers can bypass proxy access controls to access protected internal endpoints by crafting specific headers in Rack::Sendfile.","url":"https://insights.sbomify.com/CVE-2025-61780/"}