{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53795 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53795 is a high-severity path traversal vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-53795 and fix it if it is affected.\n\nWhat it is: CVE-2026-53795 is a high-severity path traversal vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-53795 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-53795/ (Markdown: https://insights.sbomify.com/CVE-2026-53795/index.md)","id":"CVE-2026-53795","markdown":"https://insights.sbomify.com/CVE-2026-53795/index.md","name":"CVE-2026-53795","record":{"aliases":["ALPINE-CVE-2026-53795","AZL-95774","BELL-CVE-2026-53795","DEBIAN-CVE-2026-53795","ECHO-3711-8d22-1254","GHSA-m9vj-637x-v6pq","ROOT-OS-DEBIAN-11-CVE-2026-53795","UBUNTU-CVE-2026-53795"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"rsync file synchronization","requires_auth":"none","summary":"Attackers can write files to arbitrary locations outside the destination tree by exploiting path traversal in rsync's temp-dir or link-dest options.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rsync","vendor":"samba"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/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 an arbitrary file write vulnerability that allows attackers to write files outside the intended destination tree by specifying an absolute path via --temp-dir or --link-dest options. The rename-confinement logic is bypassed when these options resolve to paths outside the destination tree, enabling attacker-controlled values to write files to arbitrary locations accessible to the rsync process.","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 Arbitrary File Write via --temp-dir/--link-dest","id":"CVE-2026-53795","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 TOCTOU Race Condition via Destination Directory Handling","id":"CVE-2026-53796"},"packages":[],"prev":{"headline":"rsync \u003c 3.5.0 Denial of Service via --max-alloc=0 Logic Error","id":"CVE-2026-53794"},"products":["rsync"],"published":"2026-08-13","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-15994","kev_date_added":null,"published":"2017-10-29"},{"cvss_score":9.1,"headline":"rsync \u003c 3.5.0 Daemon IP Spoofing via PROXY Protocol Header","id":"CVE-2026-53791","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.8,"headline":"rsync 3.2.5 \u003c 3.5.0 Heap Out-of-Bounds Write via files-from Entry","id":"CVE-2026-70461","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.7,"headline":"rsync 3.4.2 \u003c 3.5.0 DoS via --zt Zstandard Compression Thread Exhaustion","id":"CVE-2026-70455","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.6,"headline":"rsync 3.1.0 \u003c 3.5.0 Authorization Bypass via auth users Directive Parsing","id":"CVE-2026-70463","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.5,"headline":"rsync \u003c 3.5.0 Symlink Following Arbitrary File Overwrite","id":"CVE-2026-53803","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.4,"headline":"rsync \u003c 3.5.0 Path Traversal via Symlink Module Root","id":"CVE-2026-53784","kev_date_added":null,"published":"2026-08-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["RsyncProject"]},"summary":"Attackers can write files to arbitrary locations outside the destination tree by exploiting path traversal in rsync's temp-dir or link-dest options.","url":"https://insights.sbomify.com/CVE-2026-53795/"}