Summary
Mariner
Products covered
cbl2 boost 1.76.0-4 on CBL Mariner 2.0
cbl2 ceph 16.2.10-11 on CBL Mariner 2.0
cbl2 cloud-hypervisor 32.0-7 on CBL Mariner 2.0
cbl2 cloud-hypervisor-cvm 38.0.72.2-5 on CBL Mariner 2.0
azl3 binutils 2.41-10 on Azure Linux 3.0
cbl2 erlang 25.3.2.21-5 on CBL Mariner 2.0
azl3 boost 1.83.0-2 on Azure Linux 3.0
cbl2 freetype 2.13.1-2 on CBL Mariner 2.0
Show 24 more products
azl3 cloud-hypervisor 48.0.246-4 on Azure Linux 3.0
azl3 cmake 3.30.3-13 on Azure Linux 3.0
azl3 erlang 26.2.5.18-1 on Azure Linux 3.0
azl3 freetype 2.13.2-2 on Azure Linux 3.0
azl3 gdb 13.2-6 on Azure Linux 3.0
cbl2 keras 2.11.0-3 on CBL Mariner 2.0
cbl2 libgit2 1.6.5-1 on CBL Mariner 2.0
cbl2 nmap 7.93-4 on CBL Mariner 2.0
cbl2 nodejs18 18.20.3-12 on CBL Mariner 2.0
azl3 kata-containers 3.19.1.kata2-7 on Azure Linux 3.0
azl3 libgit2 1.7.2-1 on Azure Linux 3.0
cbl2 python-tensorflow-estimator 2.11.0-2 on CBL Mariner 2.0
azl3 nodejs24 24.13.0-3 on Azure Linux 3.0
cbl2 rsync 3.4.1-2 on CBL Mariner 2.0
cbl2 rubygem-mini_portile2 2.8.0-1 on CBL Mariner 2.0
cbl2 rust 1.72.0-15 on CBL Mariner 2.0
cbl2 tcl 8.6.13-3 on CBL Mariner 2.0
azl3 qtbase 6.6.3-4 on Azure Linux 3.0
azl3 rsync 3.4.1-2 on Azure Linux 3.0
azl3 rubygem-mini_portile2 2.8.4-1 on Azure Linux 3.0
azl3 rust 1.75.0-27 on Azure Linux 3.0
cbl2 zlib 1.2.13-2 on CBL Mariner 2.0
azl3 rust 1.90.0-6 on Azure Linux 3.0
azl3 tcl 8.6.13-3 on Azure Linux 3.0
Remediation
Release Notes
CVEs in this advisory 1
What changed in later vendor updates
SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.
- The vendor changed the advisory's last-updated date.
- Removed affected products: azl4 nodejs24 1:24.22.1-5.azl4 on Azure Linux 4.0.
- Added affected products: azl4 nodejs24 1:24.22.1-5.azl4 on Azure Linux 4.0.
- The vendor changed its remediation guidance.
Updates
- Published by Microsoft Security Response Center
The publication date reported by the vendor.
- Added to SecurityAlert
We collected the advisory from the official source.
- Updated by Microsoft Security Response Center
The vendor changed the advisory after it was first published.
- Confirmed at the source
Our collector saw this advisory during a later source check.