CVE-2026-54371

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
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.

attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
3.4%
KEV
Not listed

Published

June 29, 2026

Last Modified

July 6, 2026

Advisory Details (2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatattr-main-2.6.0-9.1.hum12026-07-02redhat

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

Frequently asked(5)

What is CVE-2026-54371?
CVE-2026-54371 is a high vulnerability published on June 29, 2026. attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can…
When was CVE-2026-54371 disclosed?
CVE-2026-54371 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54371 actively exploited?
CVE-2026-54371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54371?
CVE-2026-54371 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54371, 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-54371

Explore →

Is Your Infrastructure Affected by CVE-2026-54371?

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