CVE-2026-54370

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 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(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
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(10)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatrhosdt/opentelemetry-collector-rhel9:17857046362026-08-04redhat
redhatdiscovery/discovery-ui-rhel9:17848217502026-07-27redhat
redhatrhui5/rhua-rhel9:17847950762026-07-23redhat
redhatacl-0:2.4.0-1.el8_102026-07-22redhat
redhatacl-0:2.4.0-1.el9_82026-07-21redhat
redhatacl-0:2.4.0-1.el10_22026-07-21redhat
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
acl2.2.53-10 ... 2.4.0-1 (11 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
acl2.3.1-3 ... 2.4.0-1 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
acl2.3.2-2, 2.3.2-3, 2.4.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
acl2.3.2-2, 2.3.2-32.4.0-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 38× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-09-18 06:59 UTCEG score recompute
  2. 2026-09-18 06:59 UTCVendor advisory
  3. 2026-09-18 06:59 UTCGHSA enrichment
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-14 00:53 UTCEG score recompute
  7. 2026-09-14 00:53 UTCVendor advisory
  8. 2026-09-14 00:53 UTCGHSA enrichment
  9. 2026-09-13 16:47 UTCEPSS rescore
  10. 2026-09-12 15:15 UTCEG score recompute
  11. 2026-09-12 15:15 UTCVendor advisory
  12. 2026-09-12 15:15 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-06 14:44 UTCEG score recompute
  17. 2026-09-06 14:44 UTCVendor advisory
  18. 2026-09-06 14:44 UTCGHSA enrichment
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 18:46 UTCEG score recompute
  24. 2026-08-30 18:46 UTCVendor advisory
  25. 2026-08-30 18:46 UTCGHSA enrichment
Show 75 more
  1. 2026-08-28 21:41 UTCEPSS rescore
  2. 2026-08-27 22:48 UTCEG score recompute
  3. 2026-08-27 22:48 UTCVendor advisory
  4. 2026-08-27 22:48 UTCGHSA enrichment
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-24 12:41 UTCVendor advisory
  7. 2026-08-24 12:41 UTCGHSA enrichment
  8. 2026-08-23 10:35 UTCVendor advisory
  9. 2026-08-23 10:35 UTCGHSA enrichment
  10. 2026-08-22 09:05 UTCVendor advisory
  11. 2026-08-22 09:05 UTCGHSA enrichment
  12. 2026-08-21 07:18 UTCVendor advisory
  13. 2026-08-21 07:18 UTCGHSA enrichment
  14. 2026-08-20 05:50 UTCEG score recompute
  15. 2026-08-20 05:50 UTCVendor advisory
  16. 2026-08-20 05:50 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 23:11 UTCVendor advisory
  19. 2026-08-18 23:11 UTCGHSA enrichment
  20. 2026-08-17 08:55 UTCVendor advisory
  21. 2026-08-17 08:55 UTCGHSA enrichment
  22. 2026-08-16 07:27 UTCEG score recompute
  23. 2026-08-16 07:27 UTCVendor advisory
  24. 2026-08-16 07:27 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 05:59 UTCEG score recompute
  27. 2026-08-15 05:59 UTCVendor advisory
  28. 2026-08-15 05:59 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 04:31 UTCEG score recompute
  31. 2026-08-14 04:31 UTCVendor advisory
  32. 2026-08-14 04:31 UTCGHSA enrichment
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-13 03:02 UTCVendor advisory
  35. 2026-08-13 03:02 UTCGHSA enrichment
  36. 2026-08-12 01:34 UTCVendor advisory
  37. 2026-08-12 01:34 UTCGHSA enrichment
  38. 2026-08-11 00:06 UTCVendor advisory
  39. 2026-08-11 00:06 UTCGHSA enrichment
  40. 2026-08-09 22:38 UTCEG score recompute
  41. 2026-08-09 22:38 UTCVendor advisory
  42. 2026-08-09 22:38 UTCGHSA enrichment
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 21:10 UTCEG score recompute
  45. 2026-08-08 21:10 UTCVendor advisory
  46. 2026-08-08 21:10 UTCGHSA enrichment
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-07 19:41 UTCVendor advisory
  49. 2026-08-07 19:41 UTCGHSA enrichment
  50. 2026-08-06 18:13 UTCEG score recompute
  51. 2026-08-06 18:13 UTCVendor advisory
  52. 2026-08-06 18:13 UTCGHSA enrichment
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-05 16:45 UTCEG score recompute
  56. 2026-08-05 16:45 UTCVendor advisory
  57. 2026-08-05 16:44 UTCGHSA enrichment
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 14:46 UTCEG score recompute
  60. 2026-08-04 14:46 UTCVendor advisory
  61. 2026-08-04 14:46 UTCGHSA enrichment
  62. 2026-08-04 10:39 UTCEPSS rescore
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 07:46 UTCVendor advisory
  65. 2026-08-03 07:46 UTCGHSA enrichment
  66. 2026-08-02 04:11 UTCEG score recompute
  67. 2026-08-02 04:11 UTCVendor advisory
  68. 2026-08-02 04:11 UTCGHSA enrichment
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-08-01 02:42 UTCVendor advisory
  71. 2026-08-01 02:42 UTCGHSA enrichment
  72. 2026-07-31 01:10 UTCEG score recompute
  73. 2026-07-31 01:10 UTCVendor advisory
  74. 2026-07-31 01:10 UTCGHSA enrichment
  75. 2026-07-30 16:28 UTCEPSS rescore

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% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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