Hi, On Fri, Nov 13, 2026 at 5:27 PM Guido Günther <[email protected]> wrote: > > Hi Salvatore, > On Fri, Nov 13, 2026 at 10:19:09AM +0100, Salvatore Bonaccorso wrote: > > Hi Guido, > > > > On Thu, Nov 12, 2026 at 07:59:05PM +0100, Guido Günther wrote: > > > Hi Salvatore, > > > On Thu, Sep 17, 2026 at 08:29:05AM +0200, Salvatore Bonaccorso wrote: > > > > Source: network-manager-iodine > > > > Version: 1.2.0-3.3 > > > > Severity: grave > > > > Tags: security upstream > > > > Justification: user security hole > > > > Forwarded: > > > > https://gitlab.gnome.org/GNOME/network-manager-iodine/-/work_items/4 > > > > X-Debbugs-Cc: [email protected], Debian Security Team > > > > <[email protected]> > > > > > > > > Hi, > > > > > > > > The following vulnerability was published for network-manager-iodine. > > > > > > > > CVE-2026-91837[0]: > > > > | network-manager-iodine: Option confusion reaches iodine's pre-drop > > > > | root shell > > > > > > Should the Trixie update happen via s.d.o or via a stable update? > > > > We have network-manager-iodine in our dsa-needed list, so a DSA is > > fine, but we have some backlog to handle. Can you prepare an update? > > The alternative is defintively as well given the timing a point > > release, but SRM would need to accept the upload this upcoming > > weekend, and I know they have as well quite some substantial load. So > > let's stick I guess to the orginal plan of releasing a DSA. > > I have the package for trixie already prepared. Diff is attached, > there's no urgency. Just let me know if this looks o.k. and if I should > upload to security-master directly or if DSA wants to pick it up > (whatever is the *least* effor for you). >
The debdiff looks good to me, please upload to security-master with source tarball included (build with -sa option), targeting trixie-security distribution. I'll handle the release of a DSA, thanks! Cheers, Aron

