Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 598
Alerts This Week
Warning Icon 1 598

Stay Secure with the Latest Linux Advisories

Filter%20icon Refine advisories
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":0,"type":"x","order":4,"pct":0,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security advisories

We found 3 articles for you...
89

Fedora 43 perl-Crypt-DSA Critical Key Generation Flaw CVE-2026-14570

This update, to the current upstream release, addresses a cryptographic flaw (modulo bias) in key generation that could lead to private key compromise (CVE-2026-14570) .. -------------------------------------------------------------------------------- Fedora Update Notification FEDORA-2026-b77b9c5f04 2026-07-12 00:58:35.903674+00:00 -------------------------------------------------------------------------------- Name : perl-Crypt-DSA Product : Fedora 43 Version : 1.22 Release : 1.fc43 URL : https://metacpan.org/release/Crypt-DSA Summary : Perl module for DSA signatures and key generation Description : Crypt::DSA is an implementation of the DSA (Digital Signature Algorithm) signature verification system. This package provides DSA signing, signature verification, and key generation. DSA (Digital Signature Algorithm) signatures are no longer considered to be adequate for security. This module should only be used for verifying old signatures and should not be used for new signatures. That being said, some technologies still require DSA signatures even now. Consider using other solutions or explicitly not using DSA signatures. Crypt-DSA-GMP is a possible replacement. -------------------------------------------------------------------------------- Update Information: This update, to the current upstream release, addresses a cryptographic flaw (modulo bias) in key generation that could lead to private key compromise (CVE-2026-14570) . -------------------------------------------------------------------------------- ChangeLog: * Fri Jul 3 2026 Paul Howarth - 1.22-1 - Update to 1.22 - Hardening: Use a fresh, independent CSPRNG witness every round - Security fix: Modulo bias in key generation (CVE-2026-14570); an attack with hundreds of signatures could lead to full private-key compromise; keys should be considered compromised and new keys should be generated * Fri Jun 19 2026 Yaakov Selkowitz - 1.21-2 - Rebuilt for OpenSSL4.0 -------------------------------------------------------------------------------- References: [ 1 ] Bug #2497529 - CVE-2026-14570 perl-Crypt-DSA: Crypt::DSA: Private key recovery due to biased random number generation [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=2497529 -------------------------------------------------------------------------------- This update can be installed with the "dnf" update program. Use su -c 'dnf upgrade --advisory FEDORA-2026-b77b9c5f04' at the command line. For more information, refer to the dnf documentation available at http://dnf.readthedocs.io/en/latest/command_ref.html#upgrade-command-label All packages are signed with the Fedora Project GPG key. More details on the GPG keys used by the Fedora Project can be found at https://fedoraproject.org/keys -------------------------------------------------------------------------------- -- _______________________________________________ package-announce mailing list -- This email address is being protected from spambots. You need JavaScript enabled to view it. To unsubscribe send an email to This email address is being protected from spambots. You need JavaScript enabled to view it. Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/This email address is being protected from spambots. You need JavaScript enabled to view it. Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new . A critical flaw in the Perl Crypt-DSA module allows for private key compromise. Immediate updates are strongly advised.. Fedora 43 security flaw, Crypt-DSA update, critical flaw in key generation. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jul 11, 2026 Critical Fedora
198

Arch Linux ASA-202106-26 Medium: Python-Websockets Private Key Leak

The package python-websockets before version 9.1-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-202106-26 ========================================= Severity: Medium Date : 2021-06-09 CVE-ID : CVE-2021-33880 Package : python-websockets Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-2040 Summary ====== The package python-websockets before version 9.1-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 9.1-1. # pacman -Syu "python-websockets> =9.1-1" The problem has been fixed upstream in version 9.1. Workaround ========= None. Description ========== The aaugustin websockets library before 9.1 for Python has an observable timing discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack. Impact ===== A remote attacker could guess HTTP Basic Authentication passwords using a timing attack. References ========= https://github.com/python-websockets/websockets/commit/547a26b685d08cac0aa64e5e65f7867ac0ea9bc0 https://security.archlinux.org/CVE-2021-33880 . The Arch Linux Security Advisory ASA-202106-27 informs users about a moderate severity vulnerability in python-httpx that may lead to information disclosure.. Arch Linux, Python Websockets, Security Advisory, Private Key Recovery, Medium Severity Issue. . Severity: Medium. LinuxSecurity.com Team

Calendar%202 Jun 11, 2021 Medium ArchLinux
202

openSUSE Leap 15.2: openSUSE-SU-2021:0384-1 Moderate: mbedtls Side Channel

An update that fixes one vulnerability is now available. . openSUSE Security Update: Security update for mbedtls ______________________________________________________________________________ Announcement ID: openSUSE-SU-2021:0384-1 Rating: moderate References: #1181468 Cross-References: CVE-2020-10932 CVSS scores: CVE-2020-10932 (NVD) : 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Affected Products: openSUSE Leap 15.2 ______________________________________________________________________________ An update that fixes one vulnerability is now available. Description: This update for mbedtls fixes the following issues: - mbedtls was updated to version 2.16.9 - CVE-2020-10932: Fixed side channel in ECC code that allowed an adversary with access to precise enough timing and memory access information (typically an untrusted operating system attacking a secure enclave) to fully recover an ECDSA private key (boo#1181468). Patch Instructions: To install this openSUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: - openSUSE Leap 15.2: zypper in -t patch openSUSE-2021-384=1 Package List: - openSUSE Leap 15.2 (i586 x86_64): libmbedcrypto3-2.16.9-lp152.2.3.1 libmbedcrypto3-debuginfo-2.16.9-lp152.2.3.1 libmbedtls12-2.16.9-lp152.2.3.1 libmbedtls12-debuginfo-2.16.9-lp152.2.3.1 libmbedx509-0-2.16.9-lp152.2.3.1 libmbedx509-0-debuginfo-2.16.9-lp152.2.3.1 mbedtls-debugsource-2.16.9-lp152.2.3.1 mbedtls-devel-2.16.9-lp152.2.3.1 - openSUSE Leap 15.2 (x86_64): libmbedcrypto3-32bit-2.16.9-lp152.2.3.1 libmbedcrypto3-32bit-debuginfo-2.16.9-lp152.2.3.1 libmbedtls12-32bit-2.16.9-lp152.2.3.1 libmbedtls12-32bit-debuginfo-2.16.9-lp152.2.3.1 libmbedx509-0-32bit-2.16.9-lp152.2.3.1 libmbedx509-0-32bit-debuginfo-2.16.9-lp152.2.3.1 References: https://www.suse.com/security/cve/CVE-2020-10932.html https://bugzilla.suse.com/1181468 . openSUSE Security Update: Security update for mbedtls ______________________________________________. update, security, fixes, vulnerability, opensuse. . LinuxSecurity.com Team

Calendar%202 Mar 05, 2021 OpenSUSE
198

Arch Linux: ASA-202007-5 Medium: Mbedtls Private Key Recovery

The package mbedtls before version 2.16.7-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-202007-5 ======================================== Severity: Medium Date : 2020-07-31 CVE-ID : CVE-2020-10932 Package : mbedtls Type : private key recovery Remote : No Link : https://security.archlinux.org/AVG-1141 Summary ====== The package mbedtls before version 2.16.7-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 2.16.7-1. # pacman -Syu "mbedtls> =2.16.7-1" The problem has been fixed upstream in version 2.16.7. Workaround ========= None. Description ========== A side channel attack has been found on the ECDSA implementation of Mbed TLS before 2.22.0, 2.16.6 and 2.7.15, allowing a local attacker with access to precise enough timing and memory access information (typically an untrusted operating system attacking a secure enclave such as SGX or the TrustZone secure world) to fully recover an ECDSA private key after observing a number of signature operations. Impact ===== A remote attacker is able to recover an ECDSA private key. References ========= https://security.archlinux.org/CVE-2020-10932 . Arch Linux advisory ASA-202108-4 outlines a moderate vulnerability in the private key management of mbedtls. It is advisable to update promptly to maintain system security.. Arch Linux, mbedtls, private key recovery. . Severity: Medium. LinuxSecurity.com Team

Calendar%202 Jul 31, 2020 Medium ArchLinux
198

Arch Linux: 202003-7 Advisory High: mbedtls Private Key Recovery

The package mbedtls before version 2.16.5-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-202003-7 ======================================== Severity: High Date : 2020-03-11 CVE-ID : CVE-2019-18222 Package : mbedtls Type : private key recovery Remote : No Link : https://security.archlinux.org/AVG-1104 Summary ====== The package mbedtls before version 2.16.5-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 2.16.5-1. # pacman -Syu "mbedtls> =2.16.5-1" The problem has been fixed upstream in version 2.16.5. Workaround ========= None. Description ========== The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto before 3.0.1 and Mbed TLS before 2.20.0, 2.16.4 or 2.7.13 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side-channel attacks. Impact ===== A local attacker can recover an ECDSA private key via side-channel attacks. References ========= https://security.archlinux.org/CVE-2019-18222 . Gentoo Linux Security Notice for mbedtls exposing high-risk private key extraction; immediate update advised.. mbedtls, private key, Arch Linux security, side-channel attack. . LinuxSecurity.com Team

Calendar%202 Mar 12, 2020 ArchLinux
198

Arch Linux: 201901-10 Medium: Go-Pie Private Key Recovery

The package go-pie before version 2:1.11.5-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-201901-10 ========================================= Severity: Medium Date : 2019-01-24 CVE-ID : CVE-2019-6486 Package : go-pie Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-859 Summary ====== The package go-pie before version 2:1.11.5-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 2:1.11.5-1. # pacman -Syu "go-pie> =2:1.11.5-1" The problem has been fixed upstream in version 1.11.5. Workaround ========= None. Description ========== Go before versions 1.10.8 and 1.11.5 has a vulnerability in the crypto/elliptic implementations of the P-521 and P-384 elliptic curves. A remote attacker can exploit this by crafting inputs that consume excessive amounts of CPU. These inputs might be delivered via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares or ECDSA signatures. In some cases, if an ECDH private key is reused more than once, the attack can also lead to key recovery. Impact ===== A remote attacker can crash the system with maliciously crafted input, or recover the private key. References ========= https://groups.google.com/forum/m/#!topic/golang-announce/mVeX35iXuSw https://github.com/golang/go/issues/29903 https://github.com/golang/go/commit/42b42f71 https://security.archlinux.org/CVE-2019-6486 . Arch Linux Security Advisory ASA-201901-10 ========================================= Severity: Mediu. package, go-pie, version, vulnerable, private, recovery, linux, secur. . Severity: Medium. LinuxSecurity.com Team

Calendar%202 Jan 28, 2019 Medium ArchLinux
198

Arch Linux: ASA-201901-11 Medium: Go Private Key Recovery

The package go before version 2:1.11.5-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-201901-11 ========================================= Severity: Medium Date : 2019-01-24 CVE-ID : CVE-2019-6486 Package : go Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-859 Summary ====== The package go before version 2:1.11.5-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 2:1.11.5-1. # pacman -Syu "go> =2:1.11.5-1" The problem has been fixed upstream in version 1.11.5. Workaround ========= None. Description ========== Go before versions 1.10.8 and 1.11.5 has a vulnerability in the crypto/elliptic implementations of the P-521 and P-384 elliptic curves. A remote attacker can exploit this by crafting inputs that consume excessive amounts of CPU. These inputs might be delivered via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares or ECDSA signatures. In some cases, if an ECDH private key is reused more than once, the attack can also lead to key recovery. Impact ===== A remote attacker can crash the system with maliciously crafted input, or recover the private key. References ========= https://groups.google.com/forum/m/#!topic/golang-announce/mVeX35iXuSw https://github.com/golang/go/issues/29903 https://github.com/golang/go/commit/42b42f71 https://security.archlinux.org/CVE-2019-6486 . Upgrade the Go package on Arch Linux urgently to address CVE-2019-6486. This high-severity vulnerability risks private key exposure for users.. Arch Linux, Security Advisory, Go Package, Private Key Recovery. . Severity: Medium. LinuxSecurity.com Team

Calendar%202 Jan 27, 2019 Medium ArchLinux
198

Arch Linux 201804-6 Medium: lib32-openssl Key Recovery Risk

The package lib32-openssl before version 1:1.1.0.h-1 is vulnerable to private key recovery. . Arch Linux Security Advisory ASA-201804-6 ======================================== Severity: Medium Date : 2018-04-15 CVE-ID : CVE-2017-3738 Package : lib32-openssl Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-551 Summary ====== The package lib32-openssl before version 1:1.1.0.h-1 is vulnerable to private key recovery. Resolution ========= Upgrade to 1:1.1.0.h-1. # pacman -Syu "lib32-openssl> =1:1.1.0.h-1" The problem has been fixed upstream in version 1.1.0.h. Workaround ========= None. Description ========== There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. Impact ===== A remote attacker might be able to recover a private key (in very unlikely cases). References ========= https://openssl-library.org/news/vulnerabilities/index.html https://openssl-library.org/news/secadv/20171207.txt https://github.com/openssl/openssl/commit/5630661aecbea5fe3c4740f5fea744a1f07a6253 https://security.archlinux.org/CVE-2017-3738 . The Arch Linux Advisory ASA-202209-7 outlines a notable vulnerability found in lib32-openssl, which raises concerns surrounding the potential compromise of private key retrieval.. lib32-openssl, Arch Linux, private key recovery. . Severity: Medium.LinuxSecurity.com Team

Calendar%202 Apr 15, 2018 Medium ArchLinux
News Add Esm H240

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":0,"type":"x","order":4,"pct":0,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200