Critical Security Update for libacl: ACL Vulnerability in Red Hat Enterprise Linux

libacl-debuginfo Updated 23 Jul 2026

Summary

23/07/2026
N/A
Yes i
High
7.1

RHSA-2026:42739: Red Hat Security Advisory: acl security update. Affects libacl-debuginfo versions < 0:2.4.0-1.el10_2. Fixed in 0:2.4.0-1.el10_2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The libacl package is a part of the Red Hat Enterprise Linux ecosystem, providing support for Access Control Lists (ACLs) which allow for more granular permissions on files and directories. This package is essential for managing user permissions beyond the traditional Unix file permissions. The recent vulnerability affects multiple components of the libacl package, including libacl-debuginfo, libacl-devel, acl, and libacl itself, making it crucial for users to address this issue promptly.

Vulnerability Detail

The vulnerability, identified as CVE-2026-54369 and CVE-2026-54370, originates from flaws in the ACL implementation that could allow unauthorized access to sensitive data. This could lead to data breaches or unauthorized modifications, posing significant risks to system integrity and confidentiality. The CVSS score of this vulnerability is 7.1, indicating a high severity level that necessitates immediate attention.

How To Fix

Minimum fixed version

0:2.4.0-1.el10_2

This is the first release that contains the fix.

sudo dnf update libacl-debuginfo

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can restrict access to sensitive files and directories by modifying permissions manually until the update is applied. This can be done using the command: 'chmod 700 /path/to/sensitive/file' to limit access to the owner only.

Conclusion

The identified vulnerabilities in the libacl package pose significant risks to system security. It is imperative for users to update their packages to the patched version to mitigate these risks. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for libacl-debuginfo →

Share this vulnerability

FAQ

The vulnerability affects the ACL implementation in libacl, potentially allowing unauthorized access to sensitive data.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

The CVSS score of this vulnerability is 7.1, indicating a high severity level.

If immediate updates are not possible, consider applying stricter file permissions as a temporary workaround.

More information can be found in the Red Hat Security Advisory RHSA-2026:42739.

Related vulnerabilities

Recent vulnerabilities recorded for libacl-debuginfo.

How To Fix

Minimum fixed version

0:2.4.0-1.el10_2

This is the first release that contains the fix.

sudo dnf update libacl-debuginfo

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback