salt: This update for salt fixes the following issues: - Security issues fixed: - CVE-2025-62349: Added minimum_auth_ve...
CVE-2025-62349 is fixed in 2 products on 1 platform, first by SUSE-SU-2025:4477-1, released December 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.
This update for salt fixes the following issues: - Security issues fixed: - CVE-2025-62349: Added minimum_auth_version to enforce security (bsc#1254257) - CVE-2025-62348: Fixed Junos module yaml loader (bsc#1254256) - Backport security fixes for vendored tornado * BDSA-2024-3438 * BDSA-2024-3439 * BDSA-2024-9026 - Other changes and bugs fixed: - Fixed TLS and x509 modules for OSes with older cryptography module - Fixed Salt for Python > 3.11 (bsc#1252285) (bsc#1252244) * Use external tornado on Python > 3.11 * Make tls and x509 to use python-cryptography * Remove usage of spwd - Fixed payload signature verification on Tumbleweed (bsc#1251776) - Fixed broken symlink on migration to Leap 16.0 (bsc#1250755) - Fixed known_hosts error on gitfs (bsc#1250520) (bsc#1227207) - Improved SL Micro 6.2 detection with grains - Reverted requirement of M2Crypto >= 0.44.0 for SUSE Family distros - Set python-CherryPy as required for python-salt-testsuite
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| salt · opensuse-leap 15.6 | 3006.0-150500.4.65.1 | SUSE-SU-2025:4477-1 | Dec 18, 2025 |
| salt · opensuse-leap 16.0 | 3006.0-160000.3.1 | OPENSUSE-SU-2026:20000-1 | Dec 23, 2025 |
| salt · sles 15.6 | 3006.0-150500.4.65.1 | SUSE-SU-2025:4477-1 | Dec 18, 2025 |
| salt · sles 15.7 | 3006.0-150700.14.13.1 | SUSE-SU-2025:4478-1 | Dec 18, 2025 |
| salt-test · opensuse-leap 15.6 | 3006.0-150500.4.65.1 | SUSE-SU-2025:4477-1 | Dec 18, 2025 |
| salt-test · opensuse-leap 16.0 | 3006.0-160000.3.1 | OPENSUSE-SU-2026:20000-1 | Dec 23, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.