CVE-2026-54369
Local privilege escalation via symlink traversal in libacl (pre-2.4.0).
Is CVE-2026-54369 being exploited?
Not confirmed. CVE-2026-54369 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-54369?
CVE-2026-54369 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54369?
Yes. A fix has been recorded for CVE-2026-54369. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54369 affect?
CVE-2026-54369 affects libacl < 2.4.0, Unix/Linux systems with ACL support. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54369?
Upgrade to libacl 2.4.0+; apply vendor patch; review ACL handling
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can replace path components with symlinks to redirect ACL reads/writes, enabling unauthorized ACL changes and privilege escalation.
Patch when possible
- affected< 2.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.