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
Trending — Patch released this week
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%CVSS: 7.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 29, 2026

Last Modified

September 14, 2026

Advisory Details (3)

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

Patch Availability(14)

Vendor / EcosystemFixed in / 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 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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 98× 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 378 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54369?
CVE-2026-54369 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-54369?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54369, 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-54369

Explore →

Is Your Infrastructure Affected by CVE-2026-54369?

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