CVE-2026-54370

🎯 CVE-2026-54370 🇪🇺 EUVD

💬 0 Diskussion 📄 .md Alle CVEs anzeigen ✕

CVE-2026-54370 | 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

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.

Klassifikation & Betroffenheit:

CWE-367 acl project acl 0 <2.4.0

Time-of-check Time-of-use (TOCTOU) Race Condition 🎯 Medium

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

🛡️ Empfohlene Mitigation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-27 · Leveraging Race Conditions via Symbolic … (High) CAPEC-29 · Leveraging Time-of-Check and Time-of-Use… (High)

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2026-55950 8.7 CVE-2025-20082 8.7 CVE-2024-53694 8.6 CVE-2024-39936 8.6 CVE-2026-24260 8.5

🩹 Patch verfügbar (OSV):

🩹 3589787cd589b34bdd9265936e17190b6d3f17d1 (Commit) 🩹 24a227d0ab8576612194f8a56c2314389adc74a5 (Commit)

🇩🇪 BSI-Sicherheitshinweise: BSI · hoch · IBM QRadar SIEM: Mehrere Schwachstellen ↗ BSI · hoch · IBM App Connect Enterprise: Mehrere Schwachstellen ↗ BSI · mittel · Red Hat Enterprise Linux (acl): Mehrere Schwachstellen ermöglichen Pri ↗

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2026

Veröffentlicht 06/2026

Heute 09.11.

CVSS-Vektor-Analyse: 7.2

AV · Angriffsvektor Lokal

AC · Komplexität Hoch

PR · Privilegien Gering

UI · Interaktion Keine

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CNA-Bewertung (VulnCheck): 7.2 CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA…

Veröffentlicht:29.06.2026

Aktualisiert:25.10.2026 21:10

Assigner (CNA):VulnCheck

EUVD-ID:EUVD-2026-40086

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-367 ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	CVEs	Anteil
≥90 %	785	0,2 %
≥50 %	3.559	0,9 %
≥10 %	13.139	3,2 %
<10 %	396.072	95,8 %

Tier

CVEs

Anteil

≥90 %

785

0,2 %

≥50 %

3.559

0,9 %

≥10 %

13.139

3,2 %

<10 %

396.072

95,8 %

7.2 HIGH

EPSS

0.1%

CVE-2026-54370 💻 Lokal 🔑 Geringe Nutzerrechte nötig

acl project

CVE-2026-54370 | 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

CWE-367 ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

vor 4 Monaten ↻ vor 3 Monaten

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub