Hi Michael, I believe it is this one: https://github.com/NLnetLabs/unbound/issues/1174 and the fix is: https://github.com/NLnetLabs/unbound/commit/fff9f62a1ec008185868a369207b0d56ffb7dcb3 (Just confirmed by Yorgos.)
There will be security release for Unbound tomorrow, so I think bundling this fix with the security update would make sense and make DNS people happy. Ondrej -- Ondřej Surý (He/Him) [email protected] A gentle nudge is always appreciated if I take a little longer to reply. > On 21. 7. 2026, at 16:46, Michael Tokarev <[email protected]> wrote: > > On 7/21/26 16:24, Ondřej Surý wrote: >> NLNetLabs had been notified, but since this is already fixed in >> the upstream packages, this needs to be expeditely fixed in Debian >> as this can cause instability in the DNS ecosystem. > > So what is the upstream bugfix? > > Thanks, > > /mjt >
