CVE-2026-54369
acl before version 2.4.0 contains a symlink traversal vulnerability …
acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc7
- cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f1
- www.vulncheck.com/advisories/acl-symlink-traversal-privilege-escalation-via-libacl-functio
- access.redhat.com/security/cve/CVE-2026-54369
- bugzilla.redhat.com/show_bug.cgi?id=2490277
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54369.json
- access.redhat.com/errata/RHSA-2026:34351
- access.redhat.com/errata/RHSA-2026:42736
- nvd.nist.gov/vuln/detail/CVE-2026-54369
- cve.org/CVERecord?id=CVE-2026-54369
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.