Loading vulnerability…
CVE-2026-54369 is a symbolic-link traversal vulnerability affecting acl before version 2.4.0. The libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() follow symbolic links during pathname resolution. A local attacker controlling any component of a pathname processed by a privileged caller can substitute a symbolic link and redirect ACL reads, writes, or default-ACL deletion to an unintended file or directory. Depending on the operation and caller privileges, exploitation can enable unauthorized ACL manipulation and local privilege escalation. The legacy interfaces retain their link-following behavior for compatibility; applications must adopt safer interfaces where appropriate.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local privilege-escalation vulnerability involving symbolic-link traversal in pathname-based libacl functions. An attacker who controls a pathname component can replace it with a symbolic link and redirect a privileged caller's operation to another file. The advisory provides updated packages, but the legacy functions retain their behavior for compatibility; applications must adopt the new symlink-controllable APIs introduced in acl 2.4.0 where appropriate.
A local privilege-escalation vulnerability in acl versions before 2.4.0. An attacker controlling a pathname component processed by a privileged caller can use symbolic links to redirect libacl ACL read or write operations to arbitrary files or directories, enabling unauthorized ACL manipulation. The advisory identifies affected acl packages in EulerOS 2.0 SP11. Nessus detects exposure using reported package versions rather than testing exploitation.
A symlink traversal vulnerability in acl versions before 2.4.0 allows local attackers controlling a pathname component to redirect a privileged caller's ACL operations to arbitrary files or directories. This enables unauthorized ACL manipulation and local privilege escalation. The advisory identifies affected acl packages on EulerOS 2.0 SP11. Nessus detects exposure using reported package versions rather than testing exploitation.
A symlink traversal vulnerability in acl versions before 2.4.0 allows local attackers controlling a pathname component to redirect a privileged caller's ACL read or write operations to arbitrary files or directories. This can enable unauthorized ACL manipulation and local privilege escalation. The advisory identifies affected acl packages on EulerOS 2.0 SP13 and recommends updating them. Nessus detects exposure using self-reported package versions rather than testing exploitation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.