{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53797 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53797 is a medium-severity vulnerability in RsyncProject rsync, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53797 and fix it if it is affected.\n\nWhat it is: CVE-2026-53797 is a medium-severity vulnerability in RsyncProject rsync, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53797 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-53797/ (Markdown: https://insights.sbomify.com/CVE-2026-53797/index.md)","id":"CVE-2026-53797","markdown":"https://insights.sbomify.com/CVE-2026-53797/index.md","name":"CVE-2026-53797","record":{"aliases":["ALPINE-CVE-2026-53797","AZL-95780","BELL-CVE-2026-53797","DEBIAN-CVE-2026-53797","ECHO-7458-dc2a-8577","GHSA-3jj3-qvc7-jp6x","UBUNTU-CVE-2026-53797"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"rsync file transfer","requires_auth":"low_privilege","summary":"An attacker can exploit a symlink race condition in rsync to read files outside the intended transfer root by manipulating parent directories.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rsync","vendor":"samba"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"rsync before 3.5.0 contains a symlink race condition vulnerability in the sender's source tree traversal that allows an attacker who can manipulate a parent directory of the source tree to redirect file reads to unintended paths. Attackers can atomically replace a parent directory component with a symlink pointing outside the source root between path resolution and file open operations to disclose file contents outside the intended transfer root.","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 Symlink Race Condition Information Disclosure","id":"CVE-2026-53797","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"rsync \u003c 3.5.0 Privilege Confusion via name-converter uid/gid mapping","id":"CVE-2026-53798"},"packages":[],"prev":{"headline":"rsync \u003c 3.5.0 TOCTOU Race Condition via Destination Directory Handling","id":"CVE-2026-53796"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["RsyncProject"]},"summary":"An attacker can exploit a symlink race condition in rsync to read files outside the intended transfer root by manipulating parent directories.","url":"https://insights.sbomify.com/CVE-2026-53797/"}