Skip to content
Heist/ feed
Back to feed
UnratedFix available

rsync: Fix of CVE-2026-53783

Type: advisorySources: OSV

- CVE-2026-53783: fix a TOCTOU escape from rrsync's restricted directory by replacing the lexical-only Perl support/rrsync with upstream's Python one, which pins each validated path component through /proc/self/fd, fails closed on path anomalies, pins the receiver option directories a peer can pivot (--backup-dir, --partial-dir, alt-dest) and denies --copy-unsafe-links, device/special creation, a peer-selected --debug, remote --files-from in write-only mode and the no-overwrite auxiliary paths inside a restricted dir - NOTE: the replacement needs the new --drop-D option, backported from upstream b607369f; it makes a receiver refuse to create devices and special files without changing the file-list encoding the way --no-D does. support/ keeps shipping as non-executable documentation, so no installed program changes behaviour unless an operator has wired rrsync as an SSH forced command. rrsync is now Python rather than Perl - NOTE: one receiver-side spelling differs from upstream deliberately: a destination that already exists and is not a directory is pinned by its parent rather than by itself, because rsync replaces such a destination by unlinking its name, which the self-pin spelling cannot support -- without this, pushing a file onto an existing file through rrsync failed. Path components above the destination stay pinned either way

Products
rsync, rsync-daemon
Affected versions
Not specified
Fixed versions
3.2.3-19.el9_2.tuxcare.els22
CVEs
CVE-2026-53783
Confirmed fixed CVEs
Not specified
Updated in this feed
1 Nov 2026, 10:48 UTC · Revision 1

Source evidence

rsync: Fix of CVE-2026-53783

core-osv · Original source

Published 22 Oct 2026, 09:05 UTC

- CVE-2026-53783: fix a TOCTOU escape from rrsync's restricted directory by replacing the lexical-only Perl support/rrsync with upstream's Python one, which pins each validated path component through /proc/self/fd, fails closed on path anomalies, pins the receiver option directories a peer can pivot (--backup-dir, --partial-dir, alt-dest) and denies --copy-unsafe-links, device/special creation, a peer-selected --debug, remote --files-from in write-only mode and the no-overwrite auxiliary paths inside a restricted dir - NOTE: the replacement needs the new --drop-D option, backported from upstream b607369f; it makes a receiver refuse to create devices and special files without changing the file-list encoding the way --no-D does. support/ keeps shipping as non-executable documentation, so no installed program changes behaviour unless an operator has wired rrsync as an SSH forced command. rrsync is now Python rather than Perl - NOTE: one receiver-side spelling differs from upstream deliberately: a destination that already exists and is not a directory is pinned by its parent rather than by itself, because rsync replaces such a destination by unlinking its name, which the self-pin spelling cannot support -- without this, pushing a file onto an existing file through rrsync failed. Path components above the destination stay pinned either way

osv:CLSA-2026-1792659934

rsync

Fixed versions: 3.2.3-19.el9_2.tuxcare.els22

rsync-daemon

Fixed versions: 3.2.3-19.el9_2.tuxcare.els22

Complete source record
{
  "id": "367f9c2178757e5b860fc1cdc2ef84ff366be258546b5c5f8e69560769f3c908",
  "url": "https://osv.dev/vulnerability/CLSA-2026-1792659934",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "rsync: Fix of CVE-2026-53783",
    "summary": "- CVE-2026-53783: fix a TOCTOU escape from rrsync's restricted directory by replacing the lexical-only Perl support/rrsync with upstream's Python one, which pins each validated path component through /proc/self/fd, fails closed on path anomalies, pins the receiver option directories a peer can pivot (--backup-dir, --partial-dir, alt-dest) and denies --copy-unsafe-links, device/special creation, a peer-selected --debug, remote --files-from in write-only mode and the no-overwrite auxiliary paths inside a restricted dir - NOTE: the replacement needs the new --drop-D option, backported from upstream b607369f; it makes a receiver refuse to create devices and special files without changing the file-list encoding the way --no-D does. support/ keeps shipping as non-executable documentation, so no installed program changes behaviour unless an operator has wired rrsync as an SSH forced command. rrsync is now Python rather than Perl - NOTE: one receiver-side spelling differs from upstream deliberately: a destination that already exists and is not a directory is pinned by its parent rather than by itself, because rsync replaces such a destination by unlinking its name, which the self-pin spelling cannot support -- without this, pushing a file onto an existing file through rrsync failed. Path components above the destination stay pinned either way",
    "evidence": "osv:CLSA-2026-1792659934",
    "products": [
      {
        "name": {
          "value": "rsync",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "3.2.3-19.el9_2.tuxcare.els22",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      },
      {
        "name": {
          "value": "rsync-daemon",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "3.2.3-19.el9_2.tuxcare.els22",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CLSA-2026-1792659934",
      "aliases": [
        "CLSA-2026-1792659934"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "3.2.3-19.el9_2.tuxcare.els22"
                }
              ]
            }
          ],
          "package": {
            "name": "rsync",
            "purl": "pkg:rpm/tuxcare/rsync?distro=almalinux-9.2",
            "ecosystem": "TuxCare:AlmaLinux:9.2"
          },
          "database_specific": {
            "source": "https://github.com/cloudlinux/tuxcare-osv/tree/main/data/els_os/almalinux9.2esu/CLSA-2026-1792659934.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "3.2.3-19.el9_2.tuxcare.els22"
                }
              ]
            }
          ],
          "package": {
            "name": "rsync-daemon",
            "purl": "pkg:rpm/tuxcare/rsync-daemon?distro=almalinux-9.2",
            "ecosystem": "TuxCare:AlmaLinux:9.2"
          },
          "database_specific": {
            "source": "https://github.com/cloudlinux/tuxcare-osv/tree/main/data/els_os/almalinux9.2esu/CLSA-2026-1792659934.json"
          }
        }
      ],
      "modified": "2026-10-26T09:31:01.977654458Z",
      "provider": "osv",
      "upstream": [
        "CVE-2026-53783"
      ],
      "references": [
        "https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1792659934.html",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-53783"
      ]
    },
    "related_cves": [
      {
        "value": "CVE-2026-53783",
        "evidence": "/upstream"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 447396,
  "published_at": "2026-10-22T09:05:45+00:00"
}