Rsync vulnerabilitiesRanked by how likely they are to be used.

Product117 versions
The short answer

Rsync is made by Samba. We track 17 published vulnerabilities in it, across 117 versions. None of them is on the list of flaws known to be exploited today. If you run Rsync, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Rsync vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Rsync's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Rsync flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 72%

    A heap-based buffer overflow flaw was found in the rsync daemon.

    CVSS9.8Published15 Jan 2025
  2. 8.8%

    A flaw was found in rsync which could be triggered when rsync compares file checksums.

    CVSS7.5Published14 Jan 2025
  3. 6.5%

    rsync 3.1.1 allows remote attackers to write to arbitrary files via a symlink attack on a file in the synchronization path.

    CVSS6.4Published12 Feb 2015
  4. 6.4%

    The parse_arguments function in options.c in rsyncd in rsync before 3.1.3 does not prevent multiple --protect-args uses, which allows remote attackers to bypass an argument-sanitization protection mechanism.

    CVSS7.5Published17 Jan 2018
  5. 5.8%

    The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character in an xattr name, which allows remote attackers to cause a denial of service (heap-based buffer...

    CVSS9.8Published6 Nov 2017
  6. 5.0%

    Buffer overflow in rsync 2.6.9 to 3.0.1, with extended attribute (xattr) support enabled, might allow remote attackers to execute arbitrary code via unknown vectors.

    CVSS7.5Published10 Apr 2008
  7. 4.7%

    A flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it.

    CVSS6.5Published14 Jan 2025
  8. 4.2%

    The check_secret function in authenticate.c in rsync 3.1.0 and earlier allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a user name which does not exist in the secrets file.

    CVSS7.8Published23 Apr 2014
  9. 3.3%

    The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon_filter_list data structure (in the recv_files function in receiver.c) and also does not apply...

    CVSS9.8Published6 Dec 2017
  10. 3.2%

    rsync 3.x before 3.0.8, when certain recursion, deletion, and ownership options are used, allows remote rsync servers to cause a denial of service (heap memory corruption and application crash) or possibly execute...

    CVSS5.1Published30 Mar 2011
Precursor Intelligence

Running Rsync? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 17 published vulnerabilities listed under the name Rsync, across 117 versions.

None of Rsync's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Rsync. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.