VulnerabilityPublished 25 Feb 2026Updated 25 Mar 2026

CVE-2026-26104: Red Hat Enterprise Linux 10 · Missing Authorization

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10udisks2	Affected–	Fixed in–
Red Hat Enterprise Linux 10.0 Extended Update Supportudisks2	Affected–	Fixed in–
Red Hat Enterprise Linux 6udisks	Affected–	Fixed in–
Red Hat Enterprise Linux 7udisks2	Affected–	Fixed in–
Red Hat Enterprise Linux 8udisks2	Affected–	Fixed in–
Red Hat Enterprise Linux 9udisks2	Affected–	Fixed in–

AI-suggested

To mitigate CVE-2026-26104, organizations should implement the following specific measures: 1) Monitor Red Hat advisories closely and apply patches or updates to the udisks daemon as soon as they are released to enforce proper authorization checks. 2) Restrict local user access to systems running Red Hat Enterprise Linux 10, especially limiting accounts with low privileges from accessing or invoking D-Bus methods related to udisks. 3) Employ mandatory access control frameworks such as SELinux or AppArmor to confine the udisks daemon and restrict its interaction with unprivileged users. 4) Audit and monitor D-Bus activity and system logs for unusual attempts to export encryption metadata. 5) Consider additional encryption layers or key management solutions that do not solely rely on LUKS headers for security. 6) Educate system administrators and users about the risks of local privilege misuse and enforce strict access controls on sensitive systems. These targeted actions go beyond generic advice by focusing on controlling local access and monitoring specific system components involved in the vulnerability.

Description

A flaw was found in the udisks storage management daemon that allows unprivileged users to back up LUKS encryption headers without authorization. The issue occurs because a privileged D-Bus method responsible for exporting encryption metadata does not perform a policy check. As a result, sensitive cryptographic metadata can be read and written to attacker-controlled locations. This weakens the confidentiality guarantees of encrypted storage volumes.

Impact

The primary impact of CVE-2026-26104 is the reduction in confidentiality of encrypted storage volumes on affected Red Hat Enterprise Linux 10 systems. Attackers with local access and low privileges can extract LUKS encryption headers, which may enable cryptanalysis or facilitate offline attacks to recover encryption keys or passphrases. This exposure could lead to unauthorized data disclosure if attackers succeed in decrypting the volumes. Although the vulnerability does not directly compromise system integrity or availability, the breach of encryption metadata undermines the foundational security of encrypted storage, potentially exposing sensitive organizational data. Organizations relying on LUKS encryption for protecting sensitive information, especially in regulated industries or critical infrastructure, face increased risk of data leakage. The requirement for local access limits remote exploitation but insider threats or compromised accounts could exploit this flaw. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 00:10 UTC

Technical details

References

Community reviews

Related threats