CVE-2026-54370

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

A fix is available — apply it.

acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.

CVSS v3
6.3
EG Score
6.3(high)
EPSS
0.6%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (3)

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

Vendor Advisories for CVE-2026-54370(1)

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 27× in last 7d / 29× 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 23:53 UTCEG score recompute
  2. 2026-07-06 23:53 UTCVendor advisory
  3. 2026-07-06 23:53 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-05 22:25 UTCEG score recompute
  7. 2026-07-05 22:25 UTCVendor advisory
  8. 2026-07-05 22:25 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 20:54 UTCEG score recompute
  12. 2026-07-04 20:54 UTCVendor advisory
  13. 2026-07-04 20:54 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 19:26 UTCEG score recompute
  17. 2026-07-03 19:26 UTCVendor advisory
  18. 2026-07-03 19:26 UTCGHSA enrichment
  19. 2026-07-02 17:58 UTCEG score recompute
  20. 2026-07-02 17:58 UTCVendor advisory
  21. 2026-07-02 17:58 UTCGHSA enrichment
  22. 2026-07-01 16:29 UTCEG score recompute
  23. 2026-07-01 16:29 UTCGHSA enrichment
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 4 more
  1. 2026-06-30 15:01 UTCEG score recompute
  2. 2026-06-30 15:01 UTCGHSA enrichment
  3. 2026-06-29 13:33 UTCEG score recompute
  4. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54370?
CVE-2026-54370 is a medium vulnerability published on June 29, 2026. acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(),…
When was CVE-2026-54370 disclosed?
CVE-2026-54370 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54370 actively exploited?
CVE-2026-54370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54370?
CVE-2026-54370 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-54370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54370, 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-54370

Explore →

Is Your Infrastructure Affected by CVE-2026-54370?

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