cve.bz

CVE-2026-70463 samba rsync: Incorrect Authorization

8.6 highEPSS 0.4%

High (8.6) in samba rsync. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
rsync 3.1.0 before 3.5.0 contains an authorization bypass in auth users directive parsing. The auth users parser uses comma-only tokenization when splitting the user list, which fails to correctly handle entries of the form @Group Name where the group name contains a space. The space within the group name causes the parser to split the entry at the space boundary, discarding the deny rule associated with the group. An authenticated user whose username or group membership would be denied by an @Group Name auth users entry can connect to a restricted module because the deny rule is silently discarded during parsing.

Severity

CVSS 4.0

8.6 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-70463 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70463?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70463?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-70463 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
RsyncProject rsyncfrom 3.1.0 through 3.4.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12rsync3.5.0+ds1-0+deb12u1DEBIAN-CVE-2026-70463
Debian13rsync3.5.0+ds1-0+deb13u1DEBIAN-CVE-2026-70463
Debian14rsync3.5.0+ds1-1DEBIAN-CVE-2026-70463
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 morersyncno fix listedUBUNTU-CVE-2026-70463
Red Hatenterprise_linux:8::baseosrsync, rsync-daemon, rsync-debuginfo and 1 more0:3.1.3-28.el8_10RHSA-2026:74095
Red Hatenterprise_linux:9::appstreamrsync-daemon, rsync-rrsync0:3.2.7-1.el9_8RHSA-2026:67462
Red Hatenterprise_linux:9::baseosrsync, rsync-debuginfo, rsync-debugsource0:3.2.7-1.el9_8RHSA-2026:67462
Red Hatenterprise_linux:10.2rsync, rsync-daemon, rsync-rrsync and 2 more0:3.5.0-3.el10_2RHSA-2026:67463
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morersync3.2.3-150400.3.34.1SUSE-SU-2026:3634-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6rsync3.2.7-150600.3.24.1SUSE-SU-2026:3657-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0rsync3.4.1-160000.6.1SUSE-SU-2026:23323-1
SUSELinux Micro 6.0rsync3.2.7-8.1SUSE-SU-2026:23253-1
SUSELinux Micro 6.1rsync3.3.0-slfo.1.1_7.1SUSE-SU-2026:23254-1
SUSELinux Micro 6.2rsync3.4.1-160000.6.1SUSE-SU-2026:23289-1
openSUSELeap 16.0rsync3.4.1-160000.6.1openSUSE-SU-2026:21650-1
openSUSETumbleweedrsync3.5.1-1.1openSUSE-SU-2026:11869-1
AlmaLinux8rsync, rsync-daemon3.1.3-28.el8_10ALSA-2026:74095
AlmaLinux9rsync, rsync-daemon, rsync-rrsync3.2.7-1.el9_8ALSA-2026:67462
AlmaLinux10rsync-daemon, rsync-rrsync3.5.0-3.el10_2ALSA-2026:67463
Rocky Linux8rsync0:3.1.3-28.el8_10RLSA-2026:74095
Rocky Linux9rsync0:3.2.7-1.el9_8RLSA-2026:67462
Rocky Linux10rsync0:3.5.0-3.el10_2RLSA-2026:67463
Alpinev3.21, v3.22, v3.23 and 1 morersync3.5.0-r0ALPINE-CVE-2026-70463
Azure Linux3rsync3.5.0-1AZL-95801
Alpaquita23, 25, streamrsync3.5.0-r0BELL-CVE-2026-70463

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is an Important authorization bypass in rsync, affecting configurations that utilize the `auth users` directive with group names containing spaces. The flaw allows an authenticated, but unauthorized, user to access restricted rsync modules due to incorrect parsing of deny rules. This bypass occurs because the rsync parser fails to properly tokenize group names with embedded spaces, silently discarding intended access restrictions.

Red Hat's mitigation

To prevent this authorization bypass, ensure that no group names containing spaces are used within the `auth users` directive in the `rsyncd.conf` configuration file. Review and update any existing configurations to remove spaces from group names in this directive. After making changes, restart the `rsync` service for the new configuration to take effect. For example, use `systemctl restart rsyncd` if managing the service with systemd. Note that restarting the service will temporarily interrupt active rsync operations.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10rsync-0:3.5.0-3.el10_2Fixed 2026-09-14RHSA-2026:67463
Red Hat Enterprise Linux 8rsync-0:3.1.3-28.el8_10Fixed 2026-09-30RHSA-2026:74095
Red Hat Enterprise Linux 9rsync-0:3.2.7-1.el9_8Fixed 2026-09-14RHSA-2026:67462
Red Hat OpenShift Container Platform 4.22openshift/ose-rhel-coreos-9:4.22.9.8.202609221802-0Fixed 2026-09-29RHSA-2026:71446
Red Hat Cost Management On-Premise 1costmanagement/costmanagement-ui-rhel10:1791460851Fixed 2026-10-08RHSA-2026:79357
Red Hat Enterprise Linux 6rsyncNot affected
Red Hat Enterprise Linux 7rsyncAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-70463.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Fyyre/CVE-2026-70463 Harbor Check: matches CVE 0 stars, Python, created
    Testing CVE-2026-70463 by Fyyre

References

Check your stackJSON