On this page (7 sections)
Debian published security advisory DSA-6629-1 for network-manager-iodine, the iodine VPN plugin for NetworkManager. The flaw, tracked as CVE-2026-91837, lets a local unprivileged user execute arbitrary commands as root, according to the Debian security announcement.
If you run Debian 13 (trixie) servers, workstations or shared hosting machines where several people have shell accounts, this is worth a quick check. So far the Debian advisory is the only source we have, so details beyond it are limited.
What happened
Debian's advisory says network-manager-iodine did not properly validate the nameserver setting when establishing a connection. A local, unprivileged user could abuse that to run arbitrary commands as root before the plugin drops its privileges. The issue was discovered by Andreas Gabriel Berbescu, per the advisory.
The advisory is dated November 15, 2026 in its header, while the mailing list message carries a send date of November 14, 2026. The tracked Debian bug is 1148114.
Technical background
The iodine plugin lets NetworkManager set up VPN-style tunnels carried over DNS. Like many network helpers, it starts with elevated rights to configure the connection and then lowers its privileges. The weakness sits in that early, privileged window.
The class of problem is improper input validation, often called command injection. A configuration value (here, the nameserver) is trusted and passed into something that executes commands, so a value crafted by a user can carry extra instructions. Because the code runs as root at that point, the commands do too. The advisory does not describe how the value reaches the plugin, and we are not covering exploitation details.
Who is affected
The advisory only names the stable distribution, trixie, and gives a fixed version for it. It does not list other Debian releases or other distributions, so do not assume they are safe or vulnerable. Check the Debian security tracker page for the status of other releases.
This is a local flaw, so it requires an account or code execution on the machine already. The realistic exposure is:
- Multi-user servers, jump hosts and shared workstations with network-manager-iodine installed
- Systems where a low-privilege service account or web application user could be compromised, since a local root escalation turns a small foothold into full control
- Desktop or laptop installs that include the NetworkManager iodine plugin but never use it
Servers without NetworkManager or this plugin are not in scope. Most web hosts do not install it, but it is worth confirming rather than assuming.
How to check your exposure
This read-only command, run on Debian, lists the installed version of the package. No output means it is not installed. A version older than 1.2.0-3.3+deb13u1 on trixie needs updating.
dpkg -l network-manager-iodineTo see which version your configured repositories offer, run this read-only query. Look for 1.2.0-3.3+deb13u1 or newer as the candidate.
apt-cache policy network-manager-iodineWhat to do now
Debian recommends upgrading the network-manager-iodine packages. Updating a single package does not normally require a reboot, but if the plugin is in active use, expect any iodine connection to be re-established.
apt update && apt install --only-upgrade network-manager-iodine- Run dpkg -l network-manager-iodine on each Debian host to see whether the package is installed.
- Update to 1.2.0-3.3+deb13u1 or newer on trixie systems.
- If you do not use the iodine plugin, consider removing the package through your normal change process.
- Confirm the new version with apt-cache policy network-manager-iodine.
- Review who has local accounts on affected machines and remove accounts that are no longer needed.
- Check the Debian security tracker for the status of any non-trixie release you run.
Detection and monitoring
The advisory does not mention active exploitation or indicators of compromise, so there is nothing specific to hunt for. General hygiene still applies to any local privilege escalation: review authentication logs for unexpected logins, look for new privileged accounts or unexpected changes to system files, and keep an eye on unusual NetworkManager connection definitions created by non-admin users.
Local flaws like this often matter after something else goes wrong, such as a compromised web application account. Keeping your public-facing software patched reduces the chance an attacker ever gets that first foothold. Our WordPress security checklist and guide to what to do if your website is hacked cover that side.
For ongoing awareness of Debian kernel-level fixes, see our write-up of the related DSA-6628-1 Linux kernel update.
What we do not know yet
- No CVSS score or severity rating is given in the advisory.
- The advisory does not say whether the flaw is being exploited.
- Only trixie is listed with a fixed version; other releases are not addressed in the advisory.
- Only one source, the Debian announcement, covers this so far.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
