CVE-2026-10805
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 · uneditedA flaw was found in NetworkManager. This local privilege escalation vulnerability exists in NetworkManager's dhclient backend when processing malformed Manufacturer Usage Description (MUD) URLs. A local user can exploit this flaw to escalate privileges by triggering a script via a crafted MUD URL, provided an administrator has explicitly configured NetworkManager to use dhclient. This issue does not affect default configurations of NetworkManager.
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 confidenceThis is a local privilege escalation vulnerability in NetworkManager's dhclient backend. When an administrator has explicitly configured NetworkManager to use dhclient (non-default), a local user can exploit malformed Manufacturer Usage Description (MUD) URLs to trigger an arbitrary script and gain elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NetworkManager is installedRun 'nmcli --version' or check for the NetworkManager service with 'systemctl status NetworkManager'Affected if NetworkManager is present on the system
-
Identify the DNS resolver configured in NetworkManagerCheck NetworkManager.conf for 'dns=' setting under '[main]', or run 'nmcli -f ipv4.method,ipv6.method connection show' and inspect interface profiles. Also check 'nmcli device show' for DNS configuration.Affected if DNS resolver is set to 'dhclient' or 'dhcp' (non-default) rather than the default 'systemd-resolved' or 'internal'
-
Check the NetworkManager versionRun 'nmcli --version' or query the package (e.g., 'rpm -q NetworkManager' or 'dpkg -l network-manager')Affected if The installed version has not received patches for this vulnerability (no fixed version specified in CVE data)
-
Inspect for MUD URL configurationsSearch NetworkManager configuration files and connection profiles for 'mud' or 'manufacturer-usage-description' entries in /etc/NetworkManager/, ~/.config/NetworkManager/, or connection storageAffected if MUD URLs are configured in any NetworkManager connection profile
A system is affected only if NetworkManager is installed AND configured to use dhclient as the DNS backend instead of the default systemd-resolved or internal resolver, enabling the attack vector for malformed MUD URL processing.
Generated from the published advisory. Verify against your own configuration.
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 dataAdministrators should ensure NetworkManager is not explicitly configured to use dhclient, as the default configuration is not vulnerable. Audit existing configurations and revert to defaults if dhclient has been manually configured.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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