dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2026-26104

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The udisks storage management daemon contains a privileged D-Bus method that exports LUKS encryption header metadata without performing authorization policy checks. This allows unprivileged users to read and write sensitive cryptographic metadata to attacker-controlled locations, weakening the confidentiality guarantees of encrypted volumes.

MitigationImplement proper D-Bus policy checks on the encryption header export method, restrict access to the privileged udisks D-Bus interface, or upgrade to a patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 10.0
UdisksApplication
Affected:= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed udisks version
    Run 'rpm -q udisks2' on RHEL or check package version via your system's package manager (e.g., 'dpkg -l udisks2' or 'rpm -qa | grep udisks')
    Affected if The installed version matches 2.0.0 or is equal to 10.0 for RHEL-based systems (note: the '=' indicates the specific affected version)
  2. Verify udisks D-Bus service is running
    Check for running udisksd process: 'ps aux | grep udisksd' or query D-Bus: 'dbus-send --system --dest=org.freedesktop.UDisks2 --print-reply /org/freedesktop/UDisks2 Manager.GetPlugins'
    Affected if The udisks D-Bus service is active and accessible on the system bus
  3. Confirm LUKS encryption is in use
    Check for LUKS devices: 'cryptsetup luksDump /dev/sdX' (replace X with actual device) or list LUKS devices via 'lsblk -t' and look for crypt entries
    Affected if The system uses LUKS-encrypted volumes which are managed by udisks
  4. Inspect D-Bus policy configuration
    Check /etc/dbus-1/system.d/udisks2.conf or examine D-Bus introspection: 'dbus-send --system --dest=org.freedesktop.UDisks2 --print-reply /org/freedesktop/UDisks2/org.freedesktop.UDisks2.Manager Introspect'
    Affected if The D-Bus policy allows unrestricted access to the encryption header export method without authentication or authorization checks
  5. Test unprivileged user access to the vulnerable method
    As a non-root user, attempt to query the D-Bus interface for encryption header operations or check if the org.freedesktop.UDisks2.Manager interface is accessible without privileges
    Affected if Unprivileged users can invoke the encryption header export method on the udisks D-Bus interface without authentication failure

A system is affected if it runs the specified udisks version (2.0.0 or RHEL 10.0) with the D-Bus service active and LUKS-encrypted volumes present, where the D-Bus policy permits unprivileged access to the encryption header export functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper D-Bus policy checks on the encryption header export method, restrict access to the privileged udisks D-Bus interface, or upgrade to a patched version if available.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26104 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data