Aggregator

perl-Config-General-2.68-1.fc45

4 days ago
FEDORA-2026-8a0cc9c4a2 Packages in this update:
  • perl-Config-General-2.68-1.fc45
Update description:

This is the current upstream release, which includes fixes for CVE-2026-129820 and CVE-2026-129821 relating to validation of incoming config hashes.

perl-Config-General-2.68-1.el10_3

4 days ago
FEDORA-EPEL-2026-365007d4dd Packages in this update:
  • perl-Config-General-2.68-1.el10_3
Update description:

This is the current upstream release, which includes fixes for CVE-2026-129820 and CVE-2026-129821 relating to validation of incoming config hashes.

perl-Config-General-2.68-1.fc43

4 days ago
FEDORA-2026-42f404cc99 Packages in this update:
  • perl-Config-General-2.68-1.fc43
Update description:

This is the current upstream release, which includes fixes for CVE-2026-129820 and CVE-2026-129821 relating to validation of incoming config hashes.

perl-Config-General-2.68-1.el8

4 days ago
FEDORA-EPEL-2026-527a5e6da3 Packages in this update:
  • perl-Config-General-2.68-1.el8
Update description:

This is the current upstream release, which includes fixes for CVE-2026-129820 and CVE-2026-129821 relating to validation of incoming config hashes.

perl-Config-General-2.68-1.fc44

4 days ago
FEDORA-2026-45972c1478 Packages in this update:
  • perl-Config-General-2.68-1.fc44
Update description:

This is the current upstream release, which includes fixes for CVE-2026-129820 and CVE-2026-129821 relating to validation of incoming config hashes.

USN-9132-1: apng2gif vulnerabilities

4 days 1 hour ago
Dileep Kumar Jallepalli discovered that apng2gif incorrectly handled loading APNG files, leading to an integer overflow and a heap-based buffer over-read. If a user or automated system were tricked into converting a specially crafted APNG file, an attacker could possibly use this issue to obtain sensitive information or cause a denial of service. (CVE-2017-6960) Dileep Kumar Jallepalli discovered that apng2gif did not limit the size of memory allocations when reading APNG chunks. If a user or automated system were tricked into converting a specially crafted APNG file, an attacker could possibly use this issue to cause apng2gif to crash, resulting in a denial of service. (CVE-2017-6961) Dileep Kumar Jallepalli discovered that apng2gif incorrectly handled certain chunk sizes, leading to an integer overflow and a heap-based buffer overflow. If a user or automated system were tricked into converting a specially crafted APNG file, an attacker could possibly use this issue to cause apng2gif to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2017-6962)

USN-9150-1: SWUpdate vulnerabilities

4 days 2 hours ago
It was discovered that SWUpdate did not verify that a path was a directory before cleaning it up, leading to a race condition. A local attacker could possibly use this issue to escalate privileges or install untrusted content using a signed update. (CVE-2025-41259) It was discovered that SWUpdate used untrusted certificates embedded in CMS signatures when building the certificate chain. An attacker holding a signing key from another intermediate certificate authority under the same root could possibly use this issue to install malicious updates. After this update, SWUpdate ignores certificates embedded in CMS signatures. This issue only affected Ubuntu 22.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-109399)

USN-9149-1: MiniMagick vulnerability

4 days 2 hours ago
It was discovered that MiniMagick passed the file names and URLs given to Image.open directly to Kernel#open. If an application opened an image from an untrusted file name or URL, an attacker could possibly use this issue to execute arbitrary commands.

USN-9148-1: Mechanize vulnerability

4 days 2 hours ago
It was discovered that Mechanize used Kernel#open to open local files in several methods. If an application passed untrusted input as a local file name to one of these methods, an attacker could possibly use this issue to execute arbitrary commands.

USN-9146-1: Privoxy vulnerabilities

4 days 2 hours ago
Joshua Rogers discovered that Privoxy incorrectly handled memory allocation, leading to a memory leak. An attacker could possibly use this issue to cause Privoxy to consume excessive resources, leading to a denial of service. (CVE-2021-44540) Artem Ivanov discovered that Privoxy did not properly encode template names in error pages. A remote attacker could possibly use this issue to perform cross-site scripting attacks. (CVE-2021-44543)

USN-9144-1: ngIRCd vulnerability

4 days 2 hours ago
It was discovered that ngIRCd incorrectly handled SERVER commands without a prefix, leading to an out-of-bounds read. A remote attacker could possibly use this issue to cause ngIRCd to crash, resulting in a denial of service.

USN-9143-1: Mumble vulnerability

4 days 2 hours ago
It was discovered that the Murmur server in Mumble did not rate limit certain client messages. A remote attacker could possibly use this issue to cause Murmur to hang or crash, resulting in a denial of service. This update adds a message rate limit, which can be configured with the messageburst and messagelimit settings.

USN-9004-2: OpenJDK 25 regression

4 days 15 hours ago
USN-9004-1 fixed vulnerabilities in OpenJDK 25. Unfortunately, the fix included an unnecessary debuginfo file. This update fixes the problem. We apologize for the inconvenience. Original advisory details: It was discovered that the 2D component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to read or modify sensitive data. (CVE-2026-91415) It was discovered that the Networking component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91398) It was discovered that the 2D component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91382) It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91411) It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-83395) It was discovered that the Security component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83381, CVE-2026-87294) It was discovered that the JAXP component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87290) It was discovered that the JDBC component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83387) It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91462) It was discovered that the Security component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83374) It was discovered that the Libraries component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91410) It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87292, CVE-2026-91332, CVE-2026-91451, CVE-2026-91452) It was discovered that the JSSE component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91373) It was discovered that the JAAS component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83380) It was discovered that the JAXP component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-83400) It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91463, CVE-2026-91464) It was discovered that the Lightweight HTTP Server component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91453) It was discovered that the ImageIO component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91418) It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91487) It was discovered that the Serviceability component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91374) It was discovered that the Libraries component of OpenJDK 25 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91375) It was discovered that the JDK tools component of OpenJDK 25 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91379) It was discovered that the Utility component of OpenJDK 25 did not correctly authorize users. A local attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91380) It was discovered that the ImageIO component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91334) It was discovered that the JAXP component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87367) It was discovered that the JSSE component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83376, CVE-2026-91461) It was discovered that the Serviceability component of OpenJDK 25 did not correctly authorize users. A local attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91397) It was discovered that the Sound component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91400) It was discovered that the AWT component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91335) It was discovered that the Networking component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91394) It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87291) It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83378) It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87255) It was discovered that the Security component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91333) It was discovered that the JSSE component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91403) In addition to security fixes, the updated packages contain bug fixes, new features, and possibly incompatible changes. Please see the following for more information: https://openjdk.org/groups/vulnerability/advisories/2026-10-20 https://openjdk.org/groups/vulnerability/advisories/2026-10-21 https://openjdk.org/groups/vulnerability/advisories/2026-10-24