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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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)
EPSS
3.9%
KEV
Not listed

Published

June 29, 2026

Last Modified

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

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

Patch Availability(1)

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

All Vendor Advisories

(1)

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 46× in last 7d / 50× 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.

  1. 2026-07-06 18:37 UTCEG score recompute
  2. 2026-07-06 18:37 UTCVendor advisory
  3. 2026-07-06 18:37 UTCGHSA enrichment
  4. 2026-07-06 07:05 UTCEG score recompute
  5. 2026-07-06 07:05 UTCVendor advisory
  6. 2026-07-06 07:05 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 19:34 UTCEG score recompute
  10. 2026-07-05 19:34 UTCVendor advisory
  11. 2026-07-05 19:34 UTCGHSA enrichment
  12. 2026-07-05 08:04 UTCEG score recompute
  13. 2026-07-05 08:04 UTCVendor advisory
  14. 2026-07-05 08:03 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 20:27 UTCEG score recompute
  18. 2026-07-04 20:27 UTCVendor advisory
  19. 2026-07-04 20:27 UTCGHSA enrichment
  20. 2026-07-04 08:58 UTCEG score recompute
  21. 2026-07-04 08:58 UTCVendor advisory
  22. 2026-07-04 08:58 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 21:28 UTCEG score recompute
Show 25 more
  1. 2026-07-03 21:28 UTCVendor advisory
  2. 2026-07-03 21:28 UTCGHSA enrichment
  3. 2026-07-03 09:58 UTCEG score recompute
  4. 2026-07-03 09:58 UTCVendor advisory
  5. 2026-07-03 09:58 UTCGHSA enrichment
  6. 2026-07-02 22:24 UTCEG score recompute
  7. 2026-07-02 22:24 UTCVendor advisory
  8. 2026-07-02 22:24 UTCGHSA enrichment
  9. 2026-07-02 10:54 UTCEG score recompute
  10. 2026-07-02 10:54 UTCVendor advisory
  11. 2026-07-02 10:54 UTCGHSA enrichment
  12. 2026-07-01 23:05 UTCEG score recompute
  13. 2026-07-01 23:05 UTCGHSA enrichment
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 11:35 UTCEG score recompute
  16. 2026-07-01 11:35 UTCGHSA enrichment
  17. 2026-07-01 00:06 UTCEG score recompute
  18. 2026-07-01 00:06 UTCGHSA enrichment
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 12:34 UTCEG score recompute
  21. 2026-06-30 12:34 UTCGHSA enrichment
  22. 2026-06-30 01:02 UTCEG score recompute
  23. 2026-06-30 01:02 UTCGHSA enrichment
  24. 2026-06-29 13:33 UTCEG score recompute
  25. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

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 2, 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 3.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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