{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-70457 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-70457 is a high-severity memory corruption 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-70457 and fix it if it is affected.\n\nWhat it is: CVE-2026-70457 is a high-severity memory corruption 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-70457 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-70457/ (Markdown: https://insights.sbomify.com/CVE-2026-70457/index.md)","id":"CVE-2026-70457","markdown":"https://insights.sbomify.com/CVE-2026-70457/index.md","name":"CVE-2026-70457","record":{"aliases":["ALPINE-CVE-2026-70457","AZL-95846","BELL-CVE-2026-70457","DEBIAN-CVE-2026-70457","ECHO-112e-6676-e997","GHSA-pg7g-xqmr-xpfh","ROOT-OS-DEBIAN-11-CVE-2026-70457","UBUNTU-CVE-2026-70457"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"rsync file synchronization","requires_auth":"none","summary":"An out-of-bounds write in rsync allows attackers to corrupt memory, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rsync","vendor":"samba"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"}],"description":"rsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.","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 3.2.3 \u003c 3.5.0 Out-of-Bounds Write via parse_size_arg()","id":"CVE-2026-70457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"rsync 3.0.0 \u003c 3.5.0 Out-of-Bounds Write via FLAG_HLINKED Handling","id":"CVE-2026-70458"},"packages":[],"prev":{"headline":"rsync 3.0.1 \u003c 3.5.0 Heap Out-of-Bounds Write via read_args()","id":"CVE-2026-70456"},"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 out-of-bounds write in rsync allows attackers to corrupt memory, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-70457/"}