CVE-2026-54370

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. the CNA's CVSS baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3(high)
EPSS
0.6%
KEV
Not listed

Published

June 29, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
No patch confirmed yet.
generic

acl < 2.4.0 TOCTOU Symlink Traversal via getfacl/setfacl/chacl | Advisories | VulnCheck

https://www.vulncheck.com/advisories/acl-toctou-symlink-traversal-via-getfacl-setfacl-chacl
generic

acl.git - acl

https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
generic

acl.git - acl

https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5

Vendor Advisories for CVE-2026-54370(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatacl-main-2.4.0-0.1.hum12026-07-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-16 13:18 UTCVendor advisory
  7. 2026-07-16 13:18 UTCGHSA enrichment
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 11:49 UTCVendor advisory
  11. 2026-07-15 11:49 UTCGHSA enrichment
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 10:20 UTCVendor advisory
  15. 2026-07-14 10:20 UTCGHSA enrichment
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 08:52 UTCVendor advisory
  18. 2026-07-13 08:52 UTCGHSA enrichment
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-12 07:22 UTCVendor advisory
  22. 2026-07-12 07:22 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 32 more
  1. 2026-07-11 05:53 UTCVendor advisory
  2. 2026-07-11 05:53 UTCGHSA enrichment
  3. 2026-07-10 04:24 UTCVendor advisory
  4. 2026-07-10 04:24 UTCGHSA enrichment
  5. 2026-07-09 02:50 UTCVendor advisory
  6. 2026-07-09 02:50 UTCGHSA enrichment
  7. 2026-07-08 01:21 UTCVendor advisory
  8. 2026-07-08 01:21 UTCGHSA enrichment
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 23:53 UTCVendor advisory
  12. 2026-07-06 23:53 UTCGHSA enrichment
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-05 22:25 UTCVendor advisory
  16. 2026-07-05 22:25 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 20:54 UTCVendor advisory
  20. 2026-07-04 20:54 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 19:26 UTCVendor advisory
  24. 2026-07-03 19:26 UTCGHSA enrichment
  25. 2026-07-02 17:58 UTCVendor advisory
  26. 2026-07-02 17:58 UTCGHSA enrichment
  27. 2026-07-01 16:29 UTCGHSA enrichment
  28. 2026-07-01 15:07 UTCEPSS rescore
  29. 2026-06-30 23:22 UTCEPSS rescore
  30. 2026-06-30 15:01 UTCGHSA enrichment
  31. 2026-06-29 13:33 UTCEG score recompute
  32. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54370?
CVE-2026-54370 is a medium vulnerability published on June 29, 2026. 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(),…
When was CVE-2026-54370 disclosed?
CVE-2026-54370 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54370 actively exploited?
CVE-2026-54370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54370?
CVE-2026-54370 has a CVSS v4.0 base score of 6.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54370, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54370

Explore →

Is Your Infrastructure Affected by CVE-2026-54370?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs