CVE-2026-54369

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH 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(high)
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
4%
KEV
Not listed

Published

June 29, 2026

Last Modified

July 24, 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(7)

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

Patch Availability(5)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Explore the affected products and dependency analysis for 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