{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53793 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53793 is a critical path traversal vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53793 and fix it if it is affected.\n\nWhat it is: CVE-2026-53793 is a critical path traversal vulnerability in RsyncProject rsync, published on 13 Aug 2026. 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-2026-53793 in the wild and no public exploit code.\n\nAffected product: RsyncProject rsync. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2026-53793/ (Markdown: https://insights.sbomify.com/CVE-2026-53793/index.md)","id":"CVE-2026-53793","markdown":"https://insights.sbomify.com/CVE-2026-53793/index.md","name":"CVE-2026-53793","record":{"aliases":["ALPINE-CVE-2026-53793","AZL-95798","BELL-CVE-2026-53793","DEBIAN-CVE-2026-53793","ECHO-0bd3-4392-43db","GHSA-wj7w-vh23-mm44","ROOT-OS-DEBIAN-11-CVE-2026-53793","UBUNTU-CVE-2026-53793"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"rsync file transfer","requires_auth":"none","summary":"Remote attackers can bypass chroot confinement in rsync to read or write files outside the module root when a specific path marker is present.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"rsync before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module's subtree.","ecosystems":[],"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":"rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode","id":"CVE-2026-53793","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"rsync \u003c 3.5.0 Denial of Service via --max-alloc=0 Logic Error","id":"CVE-2026-53794"},"packages":[],"prev":{"headline":"rsync \u003c 3.5.0 Out-of-Bounds Read via Zero-Length Checksum Block","id":"CVE-2026-53792"},"products":["rsync"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["RsyncProject"]},"summary":"Remote attackers can bypass chroot confinement in rsync to read or write files outside the module root when a specific path marker is present.","url":"https://insights.sbomify.com/CVE-2026-53793/"}