{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53801 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53801 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, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53801 and fix it if it is affected.\n\nWhat it is: CVE-2026-53801 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, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53801 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-53801/ (Markdown: https://insights.sbomify.com/CVE-2026-53801/index.md)","id":"CVE-2026-53801","markdown":"https://insights.sbomify.com/CVE-2026-53801/index.md","name":"CVE-2026-53801","record":{"aliases":["ALPINE-CVE-2026-53801","AZL-95789","BELL-CVE-2026-53801","DEBIAN-CVE-2026-53801","ECHO-67f1-7aad-51af","GHSA-mch3-qr4p-chgm","UBUNTU-CVE-2026-53801"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"rsync file transfer","requires_auth":"none","summary":"Attackers can exploit a symlink race condition in rsync to read files outside the intended directory root by manipulating symlinks during scanning.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rsync","vendor":"samba"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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 directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root's intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning.","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 Directory Traversal","id":"CVE-2026-53801","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 Arbitrary File Read via Symlink Following","id":"CVE-2026-53802"},"packages":[],"prev":{"headline":"rsync \u003c 3.5.0 Symlink Race Condition via --remove-source-files","id":"CVE-2026-53800"},"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":"Attackers can exploit a symlink race condition in rsync to read files outside the intended directory root by manipulating symlinks during scanning.","url":"https://insights.sbomify.com/CVE-2026-53801/"}