CVE-2026-54369: acl < 2.4.0 Symlink Traversal Privilege Escalation via libacl Functions
acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions aclgetfile(), aclsetfile(), aclextendedfile(), and acldeletedeffile() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
aclto a version that resolves this vulnerability.Fixed in 2.4.0 - Compensating control
Ensure the privileged caller processes only pathnames with trusted, non-symlink path components to prevent symlink traversal affecting libacl functions (acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file()).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-54369?
The severity of CVE-2026-54369 is rated high with a score of 7.1.
How do I fix CVE-2026-54369?
To fix CVE-2026-54369, upgrade the acl package to version 2.4.0 or later.
What is the impact of CVE-2026-54369?
CVE-2026-54369 allows local attackers to escalate privileges using symlink traversal in libacl functions.
Which versions of acl are vulnerable to CVE-2026-54369?
Versions of acl before 2.4.0 are vulnerable to CVE-2026-54369.
Who is affected by CVE-2026-54369?
Local attackers with the ability to create symbolic links are affected by CVE-2026-54369.