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

August 19, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
No patch confirmed yet.
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(11)

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
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.

Data Freshness Timeline

(refreshed 53× in last 7d / 187× 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 286 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 19, 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.0% 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.

Start Free Scan →Browse All CVEs