CVE-2026-54370: acl < 2.4.0 TOCTOU Symlink Traversal via getfacl/setfacl/chacl
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.08% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: acl project acl 2.4.0.
Low priority for now. Upgrade to acl project acl 2.4.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.
- Published
- Jun 29, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-367
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 7.2
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
acl project acl
- before 2.4.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | acl | before 2.4.0-1.el10_2 | 2.4.0-1.el10_2 |
| AlmaLinux:10 | libacl | before 2.4.0-1.el10_2 | 2.4.0-1.el10_2 |
| AlmaLinux:10 | libacl-devel | before 2.4.0-1.el10_2 | 2.4.0-1.el10_2 |
| AlmaLinux:8 | acl | before 2.4.0-1.el8_10 | 2.4.0-1.el8_10 |
| AlmaLinux:8 | libacl | before 2.4.0-1.el8_10 | 2.4.0-1.el8_10 |
| AlmaLinux:8 | libacl-devel | before 2.4.0-1.el8_10 | 2.4.0-1.el8_10 |
| AlmaLinux:9 | acl | before 2.4.0-1.el9_8 | 2.4.0-1.el9_8 |
| AlmaLinux:9 | libacl | before 2.4.0-1.el9_8 | 2.4.0-1.el9_8 |
| AlmaLinux:9 | libacl-devel | before 2.4.0-1.el9_8 | 2.4.0-1.el9_8 |
| Debian:12 | acl | from 0 | — |
| Debian:14 | acl | before 2.4.0-1 | 2.4.0-1 |
| openSUSE:Leap 16.0 | acl | before 2.4.0-160000.1.1 | 2.4.0-160000.1.1 |
| openSUSE:Leap 16.0 | attr | before 2.6.0-160000.1.1 | 2.6.0-160000.1.1 |
| openSUSE:Tumbleweed | acl | before 2.4.0-1.1 | 2.4.0-1.1 |
| Red Hat:enterprise_linux:10.2 | acl | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | acl-debuginfo | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | acl-debugsource | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | libacl | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | libacl-debuginfo | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | libacl-devel | before 0:2.4.0-1.el10_2 | 0:2.4.0-1.el10_2 |
| Red Hat:enterprise_linux:8::baseos | acl | before 0:2.4.0-1.el8_10 | 0:2.4.0-1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | acl-debuginfo | before 0:2.4.0-1.el8_10 | 0:2.4.0-1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | acl-debugsource | before 0:2.4.0-1.el8_10 | 0:2.4.0-1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | libacl | before 0:2.4.0-1.el8_10 | 0:2.4.0-1.el8_10 |
+18
Same product
acl project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-54369acl < 2.4.0 Symlink Traversal Privilege Escalation via libacl Functions33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| acl project acl | 2.4.0 | Vendor (CNA) |
| almalinux:acl | 2.4.0-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libacl | 2.4.0-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libacl-devel | 2.4.0-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:acl | 2.4.0-1 · Debian:14 | Package registry (OSV) |
| opensuse:acl | 2.4.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:attr | 2.6.0-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:acl | 0:2.4.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:acl-debuginfo | 0:2.4.0-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:acl-debugsource | 0:2.4.0-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libacl | 0:2.4.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libacl | 0:2.4.0-1.el9_8 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:libacl-debuginfo | 0:2.4.0-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libacl-devel | 0:2.4.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libacl-devel | 0:2.4.0-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:acl | 0:2.4.0-1.el9_8 · Rocky Linux:9 | Package registry (OSV) |
| suse:acl | 2.4.0-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:attr | 2.6.0-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Andrew Tridgellfinder
- Andreas Gruenbacherfinder
Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.