Low [CVE-2026-79783] Privilege Escalation via setuid/setgid metadata
This low-severity Red Hat Linux advisory covers CVE-2026-79783 affecting Cryostat 4, Red Hat Advanced Cluster Management for Kubernetes 2.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
rclone before 1.74.4 fails to mask special permission bits when applying source-supplied mode metadata in the local backend, allowing attackers to set setuid/setgid bits on attacker-controlled files.
When copying with metadata preservation from an untrusted remote, attackers can plant a setuid binary that escalates privileges to root if rclone runs as root, or to the service account user otherwise. A flaw was found in rclone.
This vulnerability allows a remote attacker to escalate privileges by manipulating file metadata. This oversight enables an attacker to set setuid or setgid bits on their controlled files, potentially leading to privilege escalation to root or the service account user if rclone is running with elevated permissions.
An attacker who controls the source of a sync operation can craft files with setuid/setgid bits set, which when synced to the destination may result in privilege escalation if the synced files are subsequently executed. Red Hat severity: Low — CVSS 3.6 (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).
Weakness: CWE-281. Affected Red Hat products: Cryostat 4; Red Hat Advanced Cluster Management for Kubernetes 2.
Red Hat does not currently list a fixing RHSA for this CVE.
- < 1.74.4
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Use rclone with the --no-update-modtime flag or explicitly strip setuid/setgid bits after syncing files from untrusted sources. Avoid syncing executable files from untrusted remotes to locations where they may be executed by privileged users.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.