PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-70463 RsyncProject CVE debrief

The CVE-2026-70463 record indicates an authorization bypass in rsync's auth users directive parsing. The issue arises from comma-only tokenization, which fails to handle group names with spaces correctly, potentially allowing unauthorized access to restricted modules. This vulnerability affects rsync versions before 3.5.0 and is classified as HIGH severity with a CVSS score of 8.6. To verify and mitigate, defenders should review auth users configurations, monitor rsync logs for anomalies, and ensure group names are properly formatted. The CVE record was published on 2026-08-13T15:20:01.513Z and has not been modified since then.

Vendor
RsyncProject
Product
rsync
CVSS
HIGH 8.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-13
Original CVE updated
2026-08-26
Advisory published
2026-08-13
Advisory updated
2026-08-26

Who should care

Administrators and users of rsync versions before 3.5.0 should be aware of this vulnerability and take necessary actions to update or mitigate the risk. This includes reviewing auth users directive configurations, verifying group memberships, and monitoring system logs for potential unauthorized access attempts. Security teams should prioritize patching or mitigating affected systems to prevent potential exploitation.

Technical summary

The auth users parser in rsync versions before 3.5.0 uses comma-only tokenization, which fails to correctly handle entries of the form @Group Name where the group name contains a space. This 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. Affected systems should be updated to version 3.5.0 or later to mitigate this vulnerability.

Defensive priority

Authenticated users may bypass authorization due to a parsing issue with the auth users directive in rsync versions before 3.5.0.

Recommended defensive actions

  • Review and update rsync installations to version 3.5.0 or later
  • Verify auth users directive configurations for potential vulnerabilities
  • Monitor rsync logs for unauthorized access attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE-2026-70463 record indicates an authorization bypass in rsync's auth users directive parsing. The issue arises from comma-only tokenization, which fails to handle group names with spaces correctly, potentially allowing unauthorized access to restricted modules. To verify, defenders should review auth users configurations, monitor rsync logs for anomalies, and ensure group names are properly formatted.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-70463 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-70463

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-70463 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-70463

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.