# CVE-2026-10805: Networkmanager: networkmanager: local privilege escalation via malformed mud urls in dhclient backend > Local attackers can escalate privileges via command injection in NetworkManager's dhclient backend when processing malformed MUD URLs, requiring non-default configuration. - **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 4 Jun 2026 - **Updated:** 25 Sep 2026 - **Also known as:** ALSA-2026:58555, ALSA-2026:58572, CLSA-2026-1787819848, CLSA-2026-1788271382, DEBIAN-CVE-2026-10805, GHSA-rwc7-7qq8-w477, OESA-2026-2822, OESA-2026-2823, OESA-2026-2824, OESA-2026-2825, OESA-2026-3038, RHSA-2026:58555, RHSA-2026:58572, RHSA-2026:61239, RHSA-2026:61243, RHSA-2026:61244, RHSA-2026:61341, RHSA-2026:61572, RHSA-2026:61580, RLSA-2026:58555, RLSA-2026:58572, UBUNTU-CVE-2026-10805 ## What is CVE-2026-10805? CVE-2026-10805 is a medium-severity command injection vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 4 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A 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. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2026-10805? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `NetworkManager` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-adsl` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-bluetooth` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-cloud-setup` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-config-server` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-dispatcher-routing-rules` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-initscripts-updown` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-libnm` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-libnm-devel` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-ovs` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-ppp` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-team` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-tui` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-wifi` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-wwan` | AlmaLinux:8 | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-adsl` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-bluetooth` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-cloud-setup` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-config-server` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-dispatcher-routing-rules` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-initscripts-updown` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-libnm` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-libnm-devel` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-ovs` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-ppp` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-team` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-tui` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-wifi` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-wwan` | AlmaLinux:9 | All versions | 1:1.54.3-5.el9_8 | | `NetworkManager-adsl-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-bluetooth-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-cloud-setup` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-cloud-setup-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-libnm-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | | `NetworkManager-ovs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-21.el8_10 | ## How do I fix CVE-2026-10805? Apply the vendor's patch. ## Is CVE-2026-10805 being exploited? There is no known exploitation of CVE-2026-10805 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-10805 and fix it if it is affected. What it is: CVE-2026-10805 is a medium-severity command injection vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 4 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-10805 in the wild and no public exploit code. Affected product: Red Hat Multicluster Engine for Kubernetes. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-10805/ (Markdown: https://insights.sbomify.com/CVE-2026-10805/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10805 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10805 - OSV: https://osv.dev/vulnerability/CVE-2026-10805 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10805/ Summaries are generated and may contain mistakes; the official description above is the record.