Aggregator

perl-Config-General-2.68-1.fc44

7 hours 5 minutes 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.

perl-Config-General-2.68-1.el10_4

7 hours 5 minutes ago
FEDORA-EPEL-2026-cbe39425ea Packages in this update:
  • perl-Config-General-2.68-1.el10_4
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-HTTP-Body-1.25-1.fc44

9 hours 56 minutes ago
FEDORA-2026-109edb4dbc Packages in this update:
  • perl-HTTP-Body-1.25-1.fc44
Update description:
  • update to 1.25
  • fixes CVE-2026-116131 CVE-2026-116132 CVE-2026-116133 CVE-2026-116134 CVE-2026-116135 CVE-2026-116285 CVE-2026-116531 CVE-2026-117500 CVE-2026-117501 CVE-2026-121006

perl-HTTP-Body-1.25-1.fc45

9 hours 56 minutes ago
FEDORA-2026-a62f059f61 Packages in this update:
  • perl-HTTP-Body-1.25-1.fc45
Update description:
  • update to 1.25
  • fixes CVE-2026-116131 CVE-2026-116132 CVE-2026-116133 CVE-2026-116134 CVE-2026-116135 CVE-2026-116285 CVE-2026-116531 CVE-2026-117500 CVE-2026-117501 CVE-2026-121006

USN-9004-2: OpenJDK 25 regression

22 hours 45 minutes 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

USN-9131-1: CRaC JDK 25 vulnerabilities

1 day 1 hour ago
It was discovered that the Security component of CRaC JDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-114820) It was discovered that the Security component of CRaC JDK 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 JSSE component of CRaC JDK 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 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 JAAS component of CRaC JDK 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 Security component of CRaC JDK 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 JDBC component of CRaC JDK 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 Networking component of CRaC JDK 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 JAXP component of CRaC JDK 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 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 JAXP component of CRaC JDK 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 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 Networking component of CRaC JDK 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 JAXP component of CRaC JDK 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 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 ImageIO component of CRaC JDK 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 AWT component of CRaC JDK 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 JSSE component of CRaC JDK 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 Serviceability component of CRaC JDK 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 CRaC JDK 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 CRaC JDK 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 CRaC JDK 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 Networking component of CRaC JDK 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 Serviceability component of CRaC JDK 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 Networking component of CRaC JDK 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 Sound component of CRaC JDK 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 Libraries component of CRaC JDK 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 2D component of CRaC JDK 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 ImageIO component of CRaC JDK 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 Lightweight HTTP Server component of CRaC JDK 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 JGSS component of CRaC JDK 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 JGSS component of CRaC JDK 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 Compiler component of CRaC JDK 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 Libraries component of CRaC JDK 25 did not correctly authorize users. A remote unauthenticated attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-101516) 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

cri-o1.35-1.35.12-1.fc43

1 day 1 hour ago
FEDORA-2026-26886b0941 Packages in this update:
  • cri-o1.35-1.35.12-1.fc43
Update description:
  • Update to release v1.35.12
  • Resolves: rhbz#2573733
  • Resolves CVE-2026-41178: rhbz#2515084

USN-9115-1: Mini-XML vulnerabilities

1 day 1 hour ago
It was discovered that Mini-XML used unbounded recursion when deleting and writing XML nodes. An attacker could possibly use these issues to cause Mini-XML to crash, resulting in a denial of service. These issues only affected Ubuntu 16.04 LTS. (CVE-2016-4570, CVE-2016-4571) It was discovered that Mini-XML incorrectly handled certain floating point values when writing XML nodes, leading to a stack-based buffer overflow. An attacker could possibly use this issue to cause Mini-XML to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2018-20004)