Your message dated Tue, 6 Oct 2026 21:01:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#1144458 closed by Thomas Goirand <[email protected]> 
(Re: ironic: CVE-2026-74250)
has caused the Debian Bug report #1144458,
regarding ironic: CVE-2026-74250
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1144458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ironic
Version: 1:35.0.1-9
Severity: important
Tags: security upstream
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>

Hi,

The following vulnerability was published for ironic.

CVE-2026-74250[0]:
| In OpenStack Ironic before 38.0.1, the autodetect deploy interface
| may fail to run cleaning immediately after enrollment with, or
| changing to, the autodetect deploy interface.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-74250
    https://www.cve.org/CVERecord?id=CVE-2026-74250
[1] https://bugs.launchpad.net/ossa/+bug/2163017

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

--- End Message ---
--- Begin Message ---
Source: ironic
Source-Version: 1:39.0.0-1

HI Thomas,

> FYI, the only affected branch for this CVE was Gazapacho, which I fixed in
> my non-official backport repository.
> 
> So, only Testing is currently affected, any other Debian release is ok, and
> Testing will be fixed when Ironic 39 migrates. Please set the security
> tracker accordingly.

Thanks for the update, appreciated! Please be bit more specific, as we
have a lot of issues to handle ;-)

So researched it again, the upstream issue references
https://opendev.org/openstack/ironic/commit/3df2664ef309ec98187d9c2f8af411609ffded78
.

I have updated the security-tracker metadata accordingly.

Regards,
Salvatore

--- End Message ---

Reply via email to