CVE-2026-54369

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
3rd
KEV
Not listed

Published

June 29, 2026

Last Modified

September 14, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
Patch available.
generic

acl < 2.4.0 Symlink Traversal Privilege Escalation via libacl Functions | Advisories | VulnCheck

https://www.vulncheck.com/advisories/acl-symlink-traversal-privilege-escalation-via-libacl-functions
generic

Version 2.4.0 - acl.git - acl

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

Add CVE-2026-54369 and CVE-2026-54370 - acl.git - acl

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

Vendor Advisories for CVE-2026-54369(20)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatacl-0:2.4.0-0.el9_6.12026-09-14redhat
redhatacl-0:2.4.0-0.el9_2.12026-09-14redhat
redhatacl-0:2.4.0-0.el9_4.12026-09-14redhat
redhatacl-0:2.4.0-0.el10_0.12026-09-08redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
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.el10_22026-07-21redhat
redhatacl-0:2.4.0-1.el9_82026-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 rangeFix by version rangeDependents
acl2.2.53-10 ... 2.4.0-1 (11 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
acl2.3.1-3 ... 2.4.0-1 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
acl2.3.2-2, 2.3.2-3, 2.4.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
acl2.3.2-2, 2.3.2-3
  • every version up to 2.4.0-1: fixed in 2.4.0-1
—

Weakness Classification(1)

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

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× 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.

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

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

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Debian:11:acl

Frequently asked(5)

What is CVE-2026-54369?
CVE-2026-54369 is a high vulnerability published on June 29, 2026. acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions aclgetfile(), aclsetfile(), aclextendedfile(), and acldeletedef_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers…
When was CVE-2026-54369 disclosed?
CVE-2026-54369 was first published on June 29, 2026, with the most recent update on September 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-54369 actively exploited?
CVE-2026-54369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54369?
CVE-2026-54369 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54369?
A fix for CVE-2026-54369 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54369 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54369

Explore →

Is Your Infrastructure Affected by CVE-2026-54369?

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

Book a Demo →Browse All CVEs